[opensuse] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
I'm installing a bunch of new leap15 systems, all real iron, with root on nfs, version 4.1. On the client, I keep getting loads of these messages: NFS: nfs4_reclaim_open_state: Lock reclaim failed! I know it's a long shot, but does anyone recognise that? -- Per Jessen, Zürich (15.5°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
I'm installing a bunch of new leap15 systems, all real iron, with root on nfs, version 4.1. On the client, I keep getting loads of these messages:
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
I know it's a long shot, but does anyone recognise that?
On the nfs server, the above is accompanied by: NFSD: client 192.168.6.102 testing state ID with incorrect client ID and receive_cb_reply: Got unrecognized reply: calldir 0x1 xpt_bc_xprt c8844800 xid 756deda5 Lots of them. I currently have just three systems in this setup. One was installed, the other two cloned. Is there maybe some sort of nfs state information I need to clear out (in the clones) ? -- Per Jessen, Zürich (16.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Per Jessen wrote:
I'm installing a bunch of new leap15 systems, all real iron, with root on nfs, version 4.1. On the client, I keep getting loads of these messages:
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
I know it's a long shot, but does anyone recognise that?
On the nfs server, the above is accompanied by:
NFSD: client 192.168.6.102 testing state ID with incorrect client ID
Well, this was an odd one. The above error seems to be caused by /etc/hostname being used by initrd when nfs-mounting the root on startup. I changed /etc/hostname and made it unique for each system, then renegerated the initrd, et voila! everything is fine. The actual hostname is set by dhcp on boot-up, it seems that ought to be the name being used, not /etc/hostname. -- Per Jessen, Zürich (17.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-05-18 13:20, Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
I'm installing a bunch of new leap15 systems, all real iron, with root on nfs, version 4.1. On the client, I keep getting loads of these messages:
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
I know it's a long shot, but does anyone recognise that?
On the nfs server, the above is accompanied by:
NFSD: client 192.168.6.102 testing state ID with incorrect client ID
Well, this was an odd one. The above error seems to be caused by /etc/hostname being used by initrd when nfs-mounting the root on startup. I changed /etc/hostname and made it unique for each system, then renegerated the initrd, et voila! everything is fine.
The actual hostname is set by dhcp on boot-up, it seems that ought to be the name being used, not /etc/hostname.
Oh! Bug, perhaps. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E. R. wrote:
On 2018-05-18 13:20, Per Jessen wrote:
Per Jessen wrote:
Per Jessen wrote:
I'm installing a bunch of new leap15 systems, all real iron, with root on nfs, version 4.1. On the client, I keep getting loads of these messages:
NFS: nfs4_reclaim_open_state: Lock reclaim failed!
I know it's a long shot, but does anyone recognise that?
On the nfs server, the above is accompanied by:
NFSD: client 192.168.6.102 testing state ID with incorrect client ID
Well, this was an odd one. The above error seems to be caused by /etc/hostname being used by initrd when nfs-mounting the root on startup. I changed /etc/hostname and made it unique for each system, then renegerated the initrd, et voila! everything is fine.
The actual hostname is set by dhcp on boot-up, it seems that ought to be the name being used, not /etc/hostname.
Oh!
Bug, perhaps.
https://bugzilla.opensuse.org/show_bug.cgi?id=1093877 -- Per Jessen, Zürich (18.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Carlos E. R. -
Per Jessen