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.
Bug 1435901 - mount.nfs: starts mount negation with v4.2 it should be v4.1
Summary: mount.nfs: starts mount negation with v4.2 it should be v4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Yongcheng Yang
Milan Navratil
URL:
Whiteboard:
: 1375259 (view as bug list)
Depends On:
Blocks: 1385242
TreeView+ depends on / blocked
 
Reported: 2017-03-25 18:25 UTC by Steve Dickson
Modified: 2021-12-10 14:58 UTC (History)
7 users (show)

Fixed In Version: nfs-utils-1.3.0-0.37.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-01 19:50:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1603591 0 low CLOSED [RFE] - Hosted-engine deployment on NFS should have option to specify exact NFS version v4.0. 2021-09-09 15:20:25 UTC
Red Hat Product Errata RHBA-2017:2233 0 normal SHIPPED_LIVE nfs-utils bug fix and enhancement update 2017-08-01 18:19:33 UTC

Internal Links: 1603591

Description Steve Dickson 2017-03-25 18:25:54 UTC 
Description of problem:

With bug 1375259 the mounting negation was bumped up
to NFS v4.2. This caused problems that are described 
in bug 1406885 an well as cause a mount renegotiation
on every with all the major enterprise server. This 
was noticed at this year's connectathon. 

The reason being they don't support v4.2 and have no
plans to do so in the foreseeable futures. 

Since the majority of these type of servers are our
customer's servers and I don't think these renegotiation
will scale very well on huge home directory servers, 
we need to dial the negation back to start at v4.1
a version that is supported by those types of servers.
Comment 3 Yongcheng Yang 2017-03-27 10:07:22 UTC 
Please note there maybe need some update for man page NFS(5).

Just a glance about it:

$ man nfs | col -b | grep -A2 "nfsvers=n"
nfsvers=n
The NFS protocol version number used to contact the server's NFS service.  If the server does not support the requested version, the mount request fails.  If this option is not specified, the client negotiates a suitable version with the server, trying version 4 first, version 3 second, and version 2 last.
Comment 4 J. Bruce Fields 2017-03-27 14:29:18 UTC 
(In reply to Steve Dickson from comment #0)
> With bug 1375259 the mounting negation was bumped up
> to NFS v4.2. This caused problems that are described 
> in bug 1406885

Agreed, we should start negotiation with 4.1 instead.

> Since the majority of these type of servers are our
> customer's servers and I don't think these renegotiation
> will scale very well on huge home directory servers, 
> we need to dial the negation back to start at v4.1
> a version that is supported by those types of servers.

However, minor version negotiation should be cheap.  The protocol only requires a single extra round trip on mount.  Our current implementation also requires a new TCP connection, and if that causes problems, we should fix it.
Comment 9 Steve Dickson 2017-06-09 15:00:08 UTC 
*** Bug 1375259 has been marked as a duplicate of this bug. ***
Comment 14 errata-xmlrpc 2017-08-01 19:50:23 UTC 
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.

https://access.redhat.com/errata/RHBA-2017:2233
Note You need to log in before you can comment on or make changes to this bug.