[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#949505: marked as done (NFS client nfs4_reclaim_open_state: unhandled error -521)

Your message dated Sat, 01 Feb 2025 15:17:37 +0100 (CET)
with message-id <20250201141737.55351BE2EE7@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #949505,
regarding NFS client nfs4_reclaim_open_state: unhandled error -521
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 owner@bugs.debian.org
immediately.)


-- 
949505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949505
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 4.19+105

During logrotation of files residing on NFS share the NFS client report error "nfs4_reclaim_open_state: unhandled error -521".
After that all the listings of the directory were hanging on IO. Only the subdirectory is affected, files and other directories out of the affected path are accessible with no issues.
Mounted with:
data.isil01.domain:/locofwd/fwd01 on /var/log/remotelogs type nfs4 (rw,nosuid,nodev,noexec,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.x.y.z,local_lock=none,addr=10.a.b.c)
Storage does not support NFS4.1, thus vers=4 used.

Following list of additional messages:
Jan 19 00:45:04 hostname kernel: [4443714.789252] NFS: nfs4_reclaim_open_state: unhandled error -521
Jan 19 00:45:04 hostname kernel: [4443715.201988] NFS: nfs4_reclaim_open_state: unhandled error -521
Jan 19 00:45:07 hostname nfsidmap[783]: nss_getpwnam: name 'root@localdomain' does not map into domain 'domain'
Jan 19 00:48:44 hostname kernel: [4443935.440497]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 00:48:44 hostname kernel: [4443935.440524]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 00:50:45 hostname kernel: [4444056.252424]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 00:50:45 hostname kernel: [4444056.252447]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 00:52:46 hostname kernel: [4444177.080276]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 00:52:46 hostname kernel: [4444177.080299]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 00:54:47 hostname kernel: [4444297.908274]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 00:54:47 hostname kernel: [4444297.908299]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 00:56:48 hostname kernel: [4444418.740935]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 00:56:48 hostname kernel: [4444418.740962]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 00:58:48 hostname kernel: [4444539.568271]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 00:58:48 hostname kernel: [4444539.568294]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 01:00:49 hostname kernel: [4444660.392945]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 01:00:49 hostname kernel: [4444660.392993]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 01:02:50 hostname kernel: [4444781.221763]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 01:02:50 hostname kernel: [4444781.221785]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 01:04:51 hostname kernel: [4444902.050367]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 01:04:51 hostname kernel: [4444902.050393]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 19 01:06:52 hostname kernel: [4445022.877976]  ? nfs_io_completion_put.part.26+0x12/0x30 [nfs]
Jan 19 01:06:52 hostname kernel: [4445022.878000]  nfs_file_fsync+0x44/0x1e0 [nfs]
Jan 20 00:00:12 hostname nfsidmap[7278]: nss_getpwnam: name 'root@localdomain' does not map into domain 'domain'

Peter

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: