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.
Description of problem:
With current version of nfs-utils, NFSv4.1 is the default.
NFS minor version 0 is ignored when specified in fstab on NFS client.
Client is trying NFSv4.1 anyway.
Version-Release number of selected component (if applicable):
Name : nfs-utils
Arch : x86_64
Epoch : 1
Version : 1.3.0
Release : 0.48.el7_4.2
How reproducible:
100%
Steps to Reproduce:
1. /etc/fstab:
10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm /mqshare nfs4 rw,bg,hard,intr,vers=4,minorversion=0,sec=sys,addr=10.30.100.220 0 0
2. mount -a
3. mount -t nfs4
4. umount /mqshare
5. /etc/fstab:
10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm /mqshare nfs4 rw,bg,hard,intr,vers=4.0,sec=sys,addr=10.30.100.220 0 0
6. mount -a
7. mount -t nfs4
Actual results:
First 'mount -t nfs4':
10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm on /mqshare type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.30.100.11,local_lock=none,addr=10.30.100.220)
Second 'mount -t nfs4':
10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm on /mqshare type nfs4 (rw,relatime,vers=4.1,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.30.100.11,local_lock=none,addr=10.30.100.220)
Expected results:
10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm on /mqshare type nfs4 (rw,relatime,vers=4.0,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.30.100.11,local_lock=none,addr=10.30.100.220)
Additional info:
Mounting manualy results in NFSv4.0.
# mount.nfs -vvvv -overs=4.0 10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm /mqshare nfs4
mount.nfs: timeout set for Mon Apr 30 10:59:46 2018
mount.nfs: trying text-based options 'vers=4.0,addr=10.30.100.220,clientaddr=10.30.100.11'
# mount -t nfs4
10.30.100.220:/FRA2-MS-UNI001_GG_91132_NFS_T1_01/mqm on /mqshare type nfs4 (rw,relatime,vers=4.0,rsize=262144,wsize=262144,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=10.30.100.11,local_lock=none,addr=10.30.100.220)
(In reply to Yves Couèque from comment #0)
Hi Yves, thanks for the bug reporting.
This problem has already been fixed in Bug 1547506. And it has also been
back-ported to RHEL-7.4 in nfs-utils-1.3.0-0.48.el7_4.3 now.
Please update your nfs-utils package to "0.48.el7_4.3" (or beyond) and
try it again.
> Description of problem:
> With current version of nfs-utils, NFSv4.1 is the default.
> NFS minor version 0 is ignored when specified in fstab on NFS client.
> Client is trying NFSv4.1 anyway.
>
>
> Version-Release number of selected component (if applicable):
> Name : nfs-utils
> Arch : x86_64
> Epoch : 1
> Version : 1.3.0
> Release : 0.48.el7_4.2
Just closing this one for now. Feel free to reopen if there's anything new.
*** This bug has been marked as a duplicate of bug 1547506 ***