Hallo, habe auf meinem NFS-Client folgendes im Log:
Feb 20 14:28:13 worker1 kernel: [351228.572185] nfs4_reclaim_open_state: 31 callbacks suppressed Feb 20 14:28:13 worker1 kernel: [351228.572186] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:13 worker1 kernel: [351228.585636] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:13 worker1 kernel: [351228.631545] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:13 worker1 kernel: [351228.796323] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:13 worker1 kernel: [351228.808233] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:13 worker1 kernel: [351228.856091] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:14 worker1 kernel: [351229.036032] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:14 worker1 kernel: [351229.086479] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:14 worker1 kernel: [351229.144081] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:14 worker1 kernel: [351229.298136] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:18 worker1 kernel: [351233.819334] nfs4_reclaim_open_state: 24 callbacks suppressed Feb 20 14:28:18 worker1 kernel: [351233.819336] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:18 worker1 kernel: [351233.862752] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:19 worker1 kernel: [351234.056101] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:19 worker1 kernel: [351234.097673] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:19 worker1 kernel: [351234.151645] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:19 worker1 kernel: [351234.321607] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:19 worker1 kernel: [351234.823038] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:19 worker1 kernel: [351234.908751] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:20 worker1 kernel: [351235.570427] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:20 worker1 kernel: [351235.615912] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:23 worker1 kernel: [351238.951428] nfs4_reclaim_open_state: 30 callbacks suppressed Feb 20 14:28:23 worker1 kernel: [351238.951429] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351238.980290] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351238.993521] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351239.050294] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351239.086874] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351239.114446] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351239.295106] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:24 worker1 kernel: [351239.836436] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:25 worker1 kernel: [351239.983099] NFS: nfs4_reclaim_open_state: Lock reclaim failed! Feb 20 14:28:25 worker1 kernel: [351240.105247] NFS: nfs4_reclaim_open_state: Lock reclaim failed!
Beim letzten Mal, als dieser Fehler auftrat, gab es am NFS-Server zeitgleich folgende Einträge (diesmal sind sie ausgeblieben)
Feb 16 04:07:18 manager1 kernel: [123541.222745] nfsd4_validate_stateid: 406 callbacks suppressed Feb 16 04:07:18 manager1 kernel: [123541.222746] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.223289] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.223833] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.224349] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.224857] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.225879] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.226431] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.226982] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.227522] NFSD: client 10.139.0.103 testing state ID with incorrect client ID Feb 16 04:07:18 manager1 kernel: [123541.228039] NFSD: client 10.139.0.103 testing state ID with incorrect client ID
# cat /etc/exports /srv/nfs4 10.139.0.103/24(rw,sync,fsid=0,crossmnt,no_subtree_check,no_root_squash) /srv/nfs4 10.139.0.104/24(rw,sync,fsid=0,crossmnt,no_subtree_check,no_root_squash) /srv/nfs4/docker 10.139.0.103/24(rw,sync,no_subtree_check,no_root_squash,nohide,insecure) /srv/nfs4/docker 10.139.0.104/24(rw,sync,no_subtree_check,no_root_squash,nohide,insecure)
# cat /etc/systemd/system/mnt-docker.mount [Unit] Description=nfs-mount /mnt/docker/ Before=docker.service After=network.target [Mount] What=10.139.0.111:/docker Where=/mnt/docker/ Type=nfs Options=rw,nfsvers=4,minorversion=2 [Install] WantedBy=multi-user.target
Die Seiten, die ich bisher im Netz gefunden habe, deuten a) auf einen Bug in einem alten Kernel (2.x) hin oder b) sind 2017 aufgetreten - aber ohne Lösung.
Hat mir jemand eine Idee, was ich hier machen könnte?