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.
On Red Hat Enterprise Linux 6, mounting an NFS export from a Windows 2012 server failed due to the fact that the Windows server contains support for the minor version 1 (v4.1) of the NFS version 4 protocol only, along with support for versions 2 and 3. The lack of the minor version 0 (v4.0) support caused Red Hat Enterprise Linux 6 clients to fail instead of rolling back to version 3 as expected. This update fixes this bug and mounting an NFS export works as expected.
Description of problem:
With RHEL6.x, NFS mounts always fail against when mount an export on
a Windows 8 server.
The reason being, Windows 8 only support v4.1 and the RHEL6
client does not auto negotiate back to v3 as expected.
Note, The Windows 8 server does indeed return the correct
error NFS4ERR_MINOR_VERS_MISMATCH(10021).
Version-Release number of selected component (if applicable):
Any and all RHEL6 releases.
How reproducible:
Always
Steps to Reproduce:
1. mount win8:/export /mnt
Actual results:
mount.nfs: mount system call failed
Expected results:
The mount to auto negotiate back to v3 and succeed.
Additional info:
Workarounds:
mount -o minorversion=1 # to used NFSv4.1
mount -o v3 # to use v3
Set the 'Nfsvers=3' variable in the "[ Server "Server_Name" ]"
section of the /etc/nfsmount.conf file
An Example will be:
[ Server "win8" ]
Nfsvers=3
Comment 2RHEL Program Management
2012-05-03 05:19:32 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
The patch that fixes the problem. Tested at the spring Bakeathon.
diff -up linux-2.6.32-278.el6.pnfsgetdevicelist.x86_64/fs/nfs/nfs4proc.c.orig linux-2.6.32-278.el6.pnfsgetdevicelist.x86_64/fs/nfs/nfs4proc.c
--- linux-2.6.32-278.el6.pnfsgetdevicelist.x86_64/fs/nfs/nfs4proc.c.orig 2012-06-05 16:47:18.000000000 -0400
+++ linux-2.6.32-278.el6.pnfsgetdevicelist.x86_64/fs/nfs/nfs4proc.c 2012-06-06 12:01:59.000000000 -0400
@@ -92,6 +92,8 @@ static int nfs4_map_errors(int err)
case -NFS4ERR_BADOWNER:
case -NFS4ERR_BADNAME:
return -EINVAL;
+ case -NFS4ERR_MINOR_VERS_MISMATCH:
+ return -EPROTONOSUPPORT;
default:
dprintk("%s could not handle NFSv4 error %d\n",
__func__, -err);
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:
On Red Hat Enterprise Linux 6, mounting an NFS export from a Windows 2012 server failed due to the fact that the Windows server contains support for the minor version 1 (v4.1) of the NFS version 4 protocol only, along with support for versions 2 and 3. The lack of the minor version 0 (v4.0) support caused Red Hat Enterprise Linux 6 clients to fail instead of rolling back to version 3 as expected. This update fixes this bug and mounting an NFS export works as expected.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0496.html
Description of problem: With RHEL6.x, NFS mounts always fail against when mount an export on a Windows 8 server. The reason being, Windows 8 only support v4.1 and the RHEL6 client does not auto negotiate back to v3 as expected. Note, The Windows 8 server does indeed return the correct error NFS4ERR_MINOR_VERS_MISMATCH(10021). Version-Release number of selected component (if applicable): Any and all RHEL6 releases. How reproducible: Always Steps to Reproduce: 1. mount win8:/export /mnt Actual results: mount.nfs: mount system call failed Expected results: The mount to auto negotiate back to v3 and succeed. Additional info: Workarounds: mount -o minorversion=1 # to used NFSv4.1 mount -o v3 # to use v3 Set the 'Nfsvers=3' variable in the "[ Server "Server_Name" ]" section of the /etc/nfsmount.conf file An Example will be: [ Server "win8" ] Nfsvers=3