Bug 628889 - [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]
Summary: [NetApp 5.6 bug] RHEL NFS clients disconnected from NetApp NFSv4 shares with:...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jiri Pirko
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 620502 642628
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-31 10:07 UTC by RHEL Program Management
Modified: 2018-11-14 17:27 UTC (History)
19 users (show)

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!
Clone Of:
Environment:
Last Closed: 2010-11-09 18:07:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0839 0 normal SHIPPED_LIVE Moderate: kernel security and bug fix update 2010-11-09 18:06:20 UTC

Description RHEL Program Management 2010-08-31 10:07:02 UTC
This bug has been copied from bug #620502 and has been proposed
to be backported to 5.5 z-stream (EUS).

Comment 14 Jiri Pirko 2010-10-16 09:05:47 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

Comment 18 errata-xmlrpc 2010-11-09 18:07:04 UTC
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

Comment 19 Martin Prpič 2010-11-11 14:00:27 UTC
    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.

Comment 20 Yuri Arabadji 2011-05-03 11:41:24 UTC
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 */

Comment 21 Harshula Jayasuriya 2011-05-05 12:44:45 UTC
Yuri, I've opened Bug 702355 (NFS: Fix build break with CONFIG_NFS_V4=n).

Comment 22 Martin Prpič 2011-05-09 11:39:08 UTC
    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.


Note You need to log in before you can comment on or make changes to this bug.