Bug 628889
| Summary: | [NetApp 5.6 bug] RHEL NFS clients disconnected from NetApp NFSv4 shares with: v4 server returned a bad sequence-id error! [rhel-5.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | RHEL Program Management <pm-rhel> |
| Component: | kernel | Assignee: | Jiri Pirko <jpirko> |
| Status: | CLOSED ERRATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.4 | CC: | andriusb, bikash, bmr, dhoward, fleite, harshula, jlayton, jpirko, jwest, pm-eus, rkhan, rrivera, samuel.li, sprabhu, steved, tao, trond.myklebust, yanwang, yuri |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The RELEASE_LOCKOWNER operation has been implemented for NFSv4 in order to avoid an exhaustion of NFS server state IDs, which could result in an NFS4ERR_RESOURCE error. Furthermore, if the NFS4ERR_RESOURCE error is returned by the NFS server, it is now handled correctly, thus preventing a possible reason for the following error:
NFS: v4 server returned a bad sequence-id error!
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-11-09 18:07:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 620502, 642628 | ||
| Bug Blocks: | |||
|
Description
RHEL Program Management
2010-08-31 10:07:02 UTC
in kernel 2.6.18-194.21.1.el5 linux-2.6-fs-nfsv4-fix-bug-when-server-returns-nfs4err_resource.patch linux-2.6-fs-nfsv4-ensure-lockowners-are-labelled-correctly.patch linux-2.6-fs-nfsv4-add-support-for-release_lockowner-operation.patch linux-2.6-fs-nfsv4-clean-up-for-lockowner-xdr-encoding.patch linux-2.6-fs-nfsv4-ensure-we-track-lock-state-in-r-w-requests.patch An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0839.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, a large number of Red Hat Enterprise Linux NFS clients mounting a NFSv4 share from a server would show the following log messages repeatedly and could no longer access the share from the server:
NFS: v4 server returned a bad sequence-id error!
With this update, the error is no longer returned.
I disagree with linux-2.6-fs-nfs-wait-for-close-before-silly-renaming.patch, it's breaking NFSv2/v3 only builds.
Here's the proposed fix:
--- fs/nfs/nfs4_fs.h.old 2011-05-03 14:36:11.000000000 +0300
+++ fs/nfs/nfs4_fs.h 2011-05-03 14:36:34.000000000 +0300
@@ -236,6 +236,7 @@
#else
#define nfs4_close_state(a, b, c) do { } while (0)
+#define nfs4_close_sync(a, b, c) do { } while (0)
#endif /* CONFIG_NFS_V4 */
#endif /* __LINUX_FS_NFS_NFS4_FS.H */
Yuri, I've opened Bug 702355 (NFS: Fix build break with CONFIG_NFS_V4=n).
Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1,5 +1,3 @@
-Previously, a large number of Red Hat Enterprise Linux NFS clients mounting a NFSv4 share from a server would show the following log messages repeatedly and could no longer access the share from the server:
+The RELEASE_LOCKOWNER operation has been implemented for NFSv4 in order to avoid an exhaustion of NFS server state IDs, which could result in an NFS4ERR_RESOURCE error. Furthermore, if the NFS4ERR_RESOURCE error is returned by the NFS server, it is now handled correctly, thus preventing a possible reason for the following error:
-NFS: v4 server returned a bad sequence-id error!
+NFS: v4 server returned a bad sequence-id error!-
-With this update, the error is no longer returned.
|