Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionOlga Kornieskaia
2023-06-26 21:08:33 UTC
Description of problem:
Netapp QA discovered hung clients during testing of NFSv4.0 mounts and server reboots on application load that opened, locked, and did IO to the files.
Specific steps are
1. Client sent a LOCK request to the server but hasn't gotten reply yet
2. Server reboots
3. Once server starts responding with errors indicating that server rebooted (ie RENEW would get NFS4ERR_STALE_CLIENT) and then the LOCK would be resent and it gets NFS4ERR_STALE_STATEID
Client then hangs. Speficically 2 threads (1 trying to do open state recovery trying to get a seqid lock but waiting forever and 2 the lock thread waiting for recovery and holding the seqid thread
This is state of threads during the hang:
Jun 23 14:08:48 localhost kernel: task:flock state:D stack:0
pid:3223 ppid:3116 flags:0x00000204
Jun 23 14:08:48 localhost kernel: Call trace:
Jun 23 14:08:48 localhost kernel: __switch_to+0xc8/0x110
Jun 23 14:08:48 localhost kernel: __schedule+0x1d8/0x524
Jun 23 14:08:48 localhost kernel: schedule+0x60/0xfc
Jun 23 14:08:48 localhost kernel: rpc_wait_bit_killable+0x1c/0x7c [sunrpc]
Jun 23 14:08:48 localhost kernel: __wait_on_bit+0x54/0x190
Jun 23 14:08:48 localhost kernel: out_of_line_wait_on_bit+0x84/0xb0
Jun 23 14:08:48 localhost kernel:
rpc_wait_for_completion_task+0x28/0x30 [sunrpc]
Jun 23 14:08:48 localhost kernel: _nfs4_do_setlk+0x210/0x410 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_proc_setlk+0xcc/0x170 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_retry_setlk+0x188/0x1d0 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_proc_lock+0xa4/0x1dc [nfsv4]
Jun 23 14:08:48 localhost kernel: do_setlk+0x68/0xf0 [nfs]
Jun 23 14:08:48 localhost kernel: nfs_flock+0x6c/0xb4 [nfs]
Jun 23 14:08:48 localhost kernel: __do_sys_flock+0x108/0x1c0
Jun 23 14:08:48 localhost kernel: __arm64_sys_flock+0x20/0x30
Jun 23 14:08:48 localhost kernel: invoke_syscall.constprop.0+0x7c/0xd0
Jun 23 14:08:48 localhost kernel: el0_svc_common.constprop.0+0x144/0x160
Jun 23 14:08:48 localhost kernel: do_el0_svc+0x2c/0xc0
Jun 23 14:08:48 localhost kernel: el0_svc+0x3c/0x1a0
Jun 23 14:08:48 localhost kernel: el0t_64_sync_handler+0xb4/0x130
Jun 23 14:08:48 localhost kernel: el0t_64_sync+0x174/0x178
Jun 23 14:08:48 localhost kernel: task:192.168.1.106-m state:D stack:0
pid:3225 ppid:2 flags:0x00000208
Jun 23 14:08:48 localhost kernel: Call trace:
Jun 23 14:08:48 localhost kernel: __switch_to+0xc8/0x110
Jun 23 14:08:48 localhost kernel: __schedule+0x1d8/0x524
Jun 23 14:08:48 localhost kernel: schedule+0x60/0xfc
Jun 23 14:08:48 localhost kernel: rpc_wait_bit_killable+0x1c/0x7c [sunrpc]
Jun 23 14:08:48 localhost kernel: __wait_on_bit+0x54/0x190
Jun 23 14:08:48 localhost kernel: out_of_line_wait_on_bit+0x84/0xb0
Jun 23 14:08:48 localhost kernel:
rpc_wait_for_completion_task+0x28/0x30 [sunrpc]
Jun 23 14:08:48 localhost kernel: nfs4_run_open_task+0x12c/0x1f0 [nfsv4]
Jun 23 14:08:48 localhost kernel:
nfs4_open_recover_helper.part.0+0xa0/0x13c [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_open_recover+0x34/0x130 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_do_open_reclaim+0xf4/0x280 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_open_reclaim+0x58/0xe0 [nfsv4]
Jun 23 14:08:48 localhost kernel: __nfs4_reclaim_open_state+0x38/0x158 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_reclaim_open_state+0x114/0x304 [nfsv4]
un 23 14:08:48 localhost kernel: nfs4_reclaim_open_state+0x114/0x304 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_do_reclaim+0x150/0x25c [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_state_manager+0x550/0x884 [nfsv4]
Jun 23 14:08:48 localhost kernel: nfs4_run_state_manager+0xa4/0x1c0 [nfsv4]
Jun 23 14:08:48 localhost kernel: kthread+0xf0/0xf4
Jun 23 14:08:48 localhost kernel: ret_from_fork+0x10/0x20
The problem was introduce by the following commit:
commit f5ea16137a3fa2858620dc9084466491c128535f "NFSv4:
Retry LOCK on OLD_STATEID during delegation return"
The solution to the problem is to revert that commit.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Hi Olga,
Could you give us a reproducer on these subjects, it is really hard
for us to perform these steps based on the abstract description.
Thanks a lot
(In reply to Zhi Li from comment #1)
> Hi Olga,
>
> Could you give us a reproducer on these subjects, it is really hard
> for us to perform these steps based on the abstract description.
>
> Thanks a lot
Client does
mount -o vers=4.0 <server>:/<volume> /mnt
flock -x /mnt/foobar sleep 60
Now you need a way on the server to reboot it before replying to the lock operation:
option 1: hack the server to delay the lock so that a reboot can be forced
option 2: use an nfs4proxy to delay the LOCK operation (either or from).
Once a lock reply is delayed, reboot the server.
Comment 5Benjamin Coddington
2023-07-11 15:29:27 UTC
(In reply to Jeff Layton from comment #4)
> I believe this patch is intended to fix the issue:
>
> https://lore.kernel.org/linux-nfs/374ab3fe691e938cda4e239748dcb6b743705a3f.
> 1688221596.git.bcodding/T/#u
Yes! I am hoping we see that in a -fixes PR for v6.5-rc2, but if the week winds out without it I'll set up MRs with just the revert.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: kernel security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2023:7077
Description of problem: Netapp QA discovered hung clients during testing of NFSv4.0 mounts and server reboots on application load that opened, locked, and did IO to the files. Specific steps are 1. Client sent a LOCK request to the server but hasn't gotten reply yet 2. Server reboots 3. Once server starts responding with errors indicating that server rebooted (ie RENEW would get NFS4ERR_STALE_CLIENT) and then the LOCK would be resent and it gets NFS4ERR_STALE_STATEID Client then hangs. Speficically 2 threads (1 trying to do open state recovery trying to get a seqid lock but waiting forever and 2 the lock thread waiting for recovery and holding the seqid thread This is state of threads during the hang: Jun 23 14:08:48 localhost kernel: task:flock state:D stack:0 pid:3223 ppid:3116 flags:0x00000204 Jun 23 14:08:48 localhost kernel: Call trace: Jun 23 14:08:48 localhost kernel: __switch_to+0xc8/0x110 Jun 23 14:08:48 localhost kernel: __schedule+0x1d8/0x524 Jun 23 14:08:48 localhost kernel: schedule+0x60/0xfc Jun 23 14:08:48 localhost kernel: rpc_wait_bit_killable+0x1c/0x7c [sunrpc] Jun 23 14:08:48 localhost kernel: __wait_on_bit+0x54/0x190 Jun 23 14:08:48 localhost kernel: out_of_line_wait_on_bit+0x84/0xb0 Jun 23 14:08:48 localhost kernel: rpc_wait_for_completion_task+0x28/0x30 [sunrpc] Jun 23 14:08:48 localhost kernel: _nfs4_do_setlk+0x210/0x410 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_proc_setlk+0xcc/0x170 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_retry_setlk+0x188/0x1d0 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_proc_lock+0xa4/0x1dc [nfsv4] Jun 23 14:08:48 localhost kernel: do_setlk+0x68/0xf0 [nfs] Jun 23 14:08:48 localhost kernel: nfs_flock+0x6c/0xb4 [nfs] Jun 23 14:08:48 localhost kernel: __do_sys_flock+0x108/0x1c0 Jun 23 14:08:48 localhost kernel: __arm64_sys_flock+0x20/0x30 Jun 23 14:08:48 localhost kernel: invoke_syscall.constprop.0+0x7c/0xd0 Jun 23 14:08:48 localhost kernel: el0_svc_common.constprop.0+0x144/0x160 Jun 23 14:08:48 localhost kernel: do_el0_svc+0x2c/0xc0 Jun 23 14:08:48 localhost kernel: el0_svc+0x3c/0x1a0 Jun 23 14:08:48 localhost kernel: el0t_64_sync_handler+0xb4/0x130 Jun 23 14:08:48 localhost kernel: el0t_64_sync+0x174/0x178 Jun 23 14:08:48 localhost kernel: task:192.168.1.106-m state:D stack:0 pid:3225 ppid:2 flags:0x00000208 Jun 23 14:08:48 localhost kernel: Call trace: Jun 23 14:08:48 localhost kernel: __switch_to+0xc8/0x110 Jun 23 14:08:48 localhost kernel: __schedule+0x1d8/0x524 Jun 23 14:08:48 localhost kernel: schedule+0x60/0xfc Jun 23 14:08:48 localhost kernel: rpc_wait_bit_killable+0x1c/0x7c [sunrpc] Jun 23 14:08:48 localhost kernel: __wait_on_bit+0x54/0x190 Jun 23 14:08:48 localhost kernel: out_of_line_wait_on_bit+0x84/0xb0 Jun 23 14:08:48 localhost kernel: rpc_wait_for_completion_task+0x28/0x30 [sunrpc] Jun 23 14:08:48 localhost kernel: nfs4_run_open_task+0x12c/0x1f0 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_open_recover_helper.part.0+0xa0/0x13c [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_open_recover+0x34/0x130 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_do_open_reclaim+0xf4/0x280 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_open_reclaim+0x58/0xe0 [nfsv4] Jun 23 14:08:48 localhost kernel: __nfs4_reclaim_open_state+0x38/0x158 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_reclaim_open_state+0x114/0x304 [nfsv4] un 23 14:08:48 localhost kernel: nfs4_reclaim_open_state+0x114/0x304 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_do_reclaim+0x150/0x25c [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_state_manager+0x550/0x884 [nfsv4] Jun 23 14:08:48 localhost kernel: nfs4_run_state_manager+0xa4/0x1c0 [nfsv4] Jun 23 14:08:48 localhost kernel: kthread+0xf0/0xf4 Jun 23 14:08:48 localhost kernel: ret_from_fork+0x10/0x20 The problem was introduce by the following commit: commit f5ea16137a3fa2858620dc9084466491c128535f "NFSv4: Retry LOCK on OLD_STATEID during delegation return" The solution to the problem is to revert that commit. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: