Your message dated Thu, 01 May 2025 14:23:23 +0200 (CEST) with message-id <20250501122323.52fd2be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #884284, regarding nfs4_reclaim_open_state: Lock reclaim failed to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 884284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: nfs-kernel-server Version: 1:1.3.4-2.1 Severity: important Dear Maintainer, NFSv4 in stretch is broken and unusable. After some time the server exporting the directories starts throwing [1130732.440356] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [1130734.801510] NFS: nfs4_reclaim_open_state: Lock reclaim failed! [1173981.176268] NFS: nfs4_reclaim_open_state: Lock reclaim failed! messages, read/writes slow down to a crawl and at the end there is no choice but to reboot the server. Restarting nfs-kernel-server, unmounting from all known clients and remouting does not help. I have now been forced to downgrade back to nfsv3 across the board. The same setup works fine with NFSv3. NFSv4 used to work perfectly fine in jessie and before that. I am not sure if this started from the stretch upgrade or after one of the stretch mid-life kernel updates (I think it is the latter). Setup: Standard mid-size classic Linux/Unix multiuser install. Server(s) exporting $HOME and other directories to a local network. Clients mount via autofs when needed. Most directories are mounted from at least 2 (usually more) clients. -- Package-specific info: -- rpcinfo -- program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100005 1 udp 58357 mountd 100005 1 tcp 37131 mountd 100005 2 udp 54135 mountd 100005 2 tcp 32951 mountd 100005 3 udp 47587 mountd 100005 3 tcp 41773 mountd 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100227 3 udp 2049 100021 1 udp 46283 nlockmgr 100021 3 udp 46283 nlockmgr 100021 4 udp 46283 nlockmgr 100021 1 tcp 40039 nlockmgr 100021 3 tcp 40039 nlockmgr 100021 4 tcp 40039 nlockmgr 100004 2 udp 856 ypserv 100004 1 udp 856 ypserv 100004 2 tcp 857 ypserv 100004 1 tcp 857 ypserv 100009 1 udp 866 yppasswdd 600100069 1 udp 874 fypxfrd 600100069 1 tcp 875 fypxfrd 100007 2 udp 969 ypbind 100007 1 udp 969 ypbind 100007 2 tcp 970 ypbind 100007 1 tcp 970 ypbind 100024 1 udp 44513 status 100024 1 tcp 58657 status -- /etc/default/nfs-kernel-server -- RPCNFSDCOUNT=8 RPCNFSDPRIORITY=0 RPCMOUNTDOPTS="--manage-gids" NEED_SVCGSSD="" RPCSVCGSSDOPTS="" -- /etc/exports -- /exports 192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide,fsid=root) 127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide,fsid=root) /exports/md0 192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide) 127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide) /exports/md1 192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide) 127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide) /exports/md2 192.168.0.0/16(rw,async,no_root_squash,no_subtree_check,nohide) 127.0.0.0/8(rw,async,no_root_squash,no_subtree_check,nohide) -- /proc/fs/nfs/exports -- # Version 1.1 # Path Client(Flags) # IPs /exports/md0 192.168.0.0/16(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,uuid=a114f04d:9e54427e:b051ce17:4dc02e9f,sec=1) /exports 192.168.0.0/16(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,fsid=0,uuid=a3734f7a:774744b7:b41d4cea:bc2a4f0f,sec=1) /exports 127.0.0.0/8(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,fsid=0,uuid=a3734f7a:774744b7:b41d4cea:bc2a4f0f,sec=1) /exports/md0 127.0.0.0/8(rw,no_root_squash,async,wdelay,nohide,no_subtree_check,uuid=a114f04d:9e54427e:b051ce17:4dc02e9f,sec=1) -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nfs-kernel-server depends on: ii init-system-helpers 1.48 ii keyutils 1.5.9-9 ii libblkid1 2.29.2-1 ii libc6 2.24-11+deb9u1 ii libcap2 1:2.25-1 ii libsqlite3-0 3.16.2-5 ii libtirpc1 0.2.5-1.2 ii libwrap0 7.6.q-26 ii lsb-base 9.20161125 ii netbase 5.4 ii nfs-common 1:1.3.4-2.1 ii ucf 3.0036 nfs-kernel-server recommends no packages. nfs-kernel-server suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi This bug was filed for a (very) old kernel or the bug is old itself without resolution. Maybe it was for a feature enablement which nobody acted on. We are sorry we were not able to timely deal with this issue. There are many open bugs for the src:linux package and thus we are closing older bugs where it's unclear if they still occur in newer versions and are still relevant to the reporter. For an overview see: https://bugs.debian.org/src:linux . If you can reproduce your issue with - the current version in unstable/testing - the latest kernel from backports or, if it was a feature addition/wishlist and still consider it relevant, then: Please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Please try to provide as much fresh details including kernel logs where relevant. In particular were an issue is coupled with specific hardware we might ask you to do additional debugging on your side as the owner of the hardware. Regards, Salvatore
--- End Message ---
