http://bugzilla.opensuse.org/show_bug.cgi?id=1093877 Bug ID: 1093877 Summary: NFSD: client 192.168.6.102 testing state ID with incorrect client ID Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: per@computer.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I am installing a number of identical systems. I installed one, then I cloned the filesystem for the others. They all have root on NFS. In the clones I amended /etc/fstab, /etc/udev/rules.d/70-persistent-net.rules and /var/lib/wicked/duid.xml, then I rebuilt the initrds. I had no problems booting system#1, but as soon as system#2 or #3 would come up, the nfs server started spewing out: kernel: [16754897.516786] NFSD: client 192.168.6.101 testing state ID with incorrect client ID kernel: [16754897.504556] nfsd4_validate_stateid: 365 callbacks suppressed kernel: [16754852.428142] receive_cb_reply: Got unrecognized reply: calldir 0x1 xpt_bc_xprt c86c0800 xid 5fa768c4 On the client I saw: NFS: nfs4_reclaim_open_state: Lock reclaim failed! Loads of them, on client and server both. It took quite a bit of debugging, but in the end the problem was that /etc/hostname was the same on all systems. When I made it unique per system, and rebuilt the initrd, no problems. I guess NFS somehow uses /etc/hostname, but shouldn't it be using /proc/sys/kernel/hostname instead? The systems are given hostnames over dhcp. -- You are receiving this mail because: You are on the CC list for the bug.