Bug 1363737
Summary: | man mount.nfs incorrectly mentions the default mount version as nfs version 3 or 2 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ameya Sathe <asathe> |
Component: | nfs-utils | Assignee: | Steve Dickson <steved> |
Status: | CLOSED ERRATA | QA Contact: | Yongcheng Yang <yoyang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.2 | CC: | eguan |
Target Milestone: | rc | ||
Target Release: | 7.3 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | nfs-utils-1.3.0-0.32.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 05:04:20 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ameya Sathe
2016-08-03 13:03:43 UTC
(In reply to Ameya Sathe from comment #0) > Description of problem: > Quoting from 'man mount.nfs': > "mount.nfs is used to mount NFS file systems versions 3 or 2" > I don't see the problem here.... because the man page also says "mount.nfs4 is used for mounting NFSv4 file system" which is the case. (In reply to Ameya Sathe from comment #0) > Description of problem: > Quoting from 'man mount.nfs': > "mount.nfs is used to mount NFS file systems versions 3 or 2" > > But, > mount.nfs nfsserver.example.com:/nfsshare /abc -v > gives the following output > > mount.nfs nfsserver.example.com:/nfsshare /abc -v > mount.nfs: timeout set for Wed Aug 3 12:43:57 2016 > mount.nfs: trying text-based options > 'vers=4,addr=10.7.241.211,clientaddr=10.27.119.29' > mount.nfs: mount(2): Permission denied > mount.nfs: access denied by server while mounting > nfsserver.example.com:/nfsshare > Maybe we need to import the upstream patch: commit d1f6583a5ff32711a1da1d4a13a29a5700f63504 Author: Ben Hutchings <ben.uk> Date: Thu Apr 2 11:43:33 2015 -0400 mount.nfs.man, nfs.man: Update distinction between fstypes From: Ben Hutchings <ben.uk> this is a resync of the man page updates in the Debian package with mainline nfs-utils. Acked-By: J. Bruce Fields <bfields> Signed-off-by: Steve Dickson <steved> And then the mount.nfs(8) will look like: "Under Linux 2.6.32 and later kernel versions, mount.nfs can mount all NFS file system versions. Under earlier Linux kernel versions, mount.nfs4 must be used for mounting NFSv4 file systems while mount.nfs must be used for NFSv3 and v2." Have checked the man page is updated as expected. Move this bug on to VERIFIED. [root@ibm-x3250m4-07 ~]# rpm -Uvh nfs-utils-1.3.0-0.32.el7.x86_64.rpm Preparing... ################################# [100%] Updating / installing... 1:nfs-utils-1:1.3.0-0.32.el7 ################################# [ 50%] Cleaning up / removing... 2:nfs-utils-1:1.3.0-0.31.el7 ################################# [100%] [root@ibm-x3250m4-07 ~]# rpm -q nfs-utils nfs-utils-1.3.0-0.32.el7.x86_64 [root@ibm-x3250m4-07 ~]# man mount.nfs | col -b MOUNT.NFS(8) System Manager's Manual MOUNT.NFS(8) NAME mount.nfs, mount.nfs4 - mount a Network File System SYNOPSIS mount.nfs remotetarget dir [-rvVwfnsh ] [-o options] DESCRIPTION mount.nfs is a part of nfs(5) utilities package, which provides NFS client functionality. mount.nfs is meant to be used by the mount(8) command for mounting NFS shares. This subcommand, however, can also be used as a stand‐ alone command with limited functionality. remotetarget is a server share usually in the form of servername:/path/to/share. dir is the directory on which the file system is to be mounted. Under Linux 2.6.32 and later kernel versions, mount.nfs can mount all NFS file system versions. Under earlier Linux kernel versions, mount.nfs4 must be used for mounting NFSv4 file systems while mount.nfs must be used for NFSv3 and v2. [snip...] 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://rhn.redhat.com/errata/RHBA-2016-2383.html |