RHEL6 or 7: NFS4.1 client with open files neglects to renew lease with SEQUENCE operation, leading to expired lease and NFS4ERR_BADSESSION errors
Issue
- On RHEL6.6 NFS client connected to a RHEL7.2 clustered NFS4.1 server, periodically we see NFS: Got error -10052 from the server on DESTROY_SESSION. Session has been destroyed regardless...
- Periodically we see
NFS4ERR_BADSESSION(10052) errors in tcpdumps with NFSv4.1 - Is there any risk of file loss or data corruption when these errors occur?
Environment
- Red Hat Enterprise Linux 6 (NFS client)
- kernels starting with 2.6.32-431*.el6 (RHEL6.5) and prior to kernel-2.6.32-696.el6
- kernels 2.6.32-358*.el6 (RHEL6.4) are not affected
- Red Hat Enterprise Linux 7 (NFS client)
- kernels prior to 3.10.0-327.el7 (RHEL7.2)
- NFS4.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
