RHEL5: NFSv4 client lockup, same NFS4 CLOSE repeats with NFS4ERR_OLD_STATEID (10024) error code
Issue
- The following is seen in messages file prior to the lockup:
Sep 2 10:09:54 hostname _k_e_r_n_e_l_: NFS: v4 server returned a bad sequence-id error!
- One process is stuck in a close() system call, waiting on NFS4 to complete the operation.
#0 [ffff8102d3e3dce8] schedule at ffffffff80062fa0
#1 [ffff8102d3e3ddc0] rpc_wait_bit_interruptible at ffffffff885f17b3 [sunrpc]
#2 [ffff8102d3e3ddd0] __wait_on_bit at ffffffff80063a0a
#3 [ffff8102d3e3de10] out_of_line_wait_on_bit at ffffffff80063aa4
#4 [ffff8102d3e3de80] nfs4_do_close at ffffffff88677065 [nfs]
#5 [ffff8102d3e3dec0] __put_nfs_open_context at ffffffff8866401a [nfs]
#6 [ffff8102d3e3dee0] nfs_release at ffffffff886640ce [nfs]
#7 [ffff8102d3e3df00] __fput at ffffffff80012c62
#8 [ffff8102d3e3df40] filp_close at ffffffff80024200
#9 [ffff8102d3e3df60] sys_close at ffffffff8001e5f8
#10 [ffff8102d3e3df80] tracesys at ffffffff8005d29e (via system_call)
Environment
- NFS Client
- Red Hat Enterprise Linux 5
- kernels prior to 2.6.18-371.11.1.el5
- NFS Server
- NetApp: Ontap 8.02P3 (7-mode)
- NFSv4
- Application which opens a file multiple times, and results in repeated sequences of the following NFSv4 operations
- OPEN, OPEN
- WRITE
- CLOSE, CLOSE
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
