Bug 609720 - Incorrect description of filesystem type used in nfs(5) man page
Summary: Incorrect description of filesystem type used in nfs(5) man page
Status: CLOSED DUPLICATE of bug 637198
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nfs-utils   
(Show other bugs)
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: J. Bruce Fields
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-30 21:54 UTC by Sachin Prabhu
Modified: 2018-11-14 19:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-01-19 19:15:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Sachin Prabhu 2010-06-30 21:54:27 UTC 
the nfs(5) man page states

--
       The fstype field contains either "nfs" (for version 2 or version 3  NFS
       mounts)  or  "nfs4"  (for NFS version 4 mounts).  The nfs and nfs4 file
       system types share similar mount options, which are described below.
--


This is incorrect. The fstype nfs can also denote NFS version 4 mounts. fstype nfsv4 is also provided for legacy reasons.
Comment 2 J. Bruce Fields 2010-11-22 16:12:12 UTC 
This is fixed in utils/mount/nfs.man of upstream nfs-utils (now reads "The fstype field contains "nfs", for whatever version of the  protocol.")  There's been a lot of work on that man page which we may want to incorporate.
Comment 3 Ric Wheeler 2010-11-22 18:43:17 UTC 
Bruce, can you pull in and update that man page for us?
Comment 6 Jeff Layton 2011-01-19 19:15:01 UTC 
Looks like this was fixed as a side-effect of Steved's rebase of
nfs-utils to 1.2.3 for bug 637198. Closing as a duplicate of that bug...

*** This bug has been marked as a duplicate of bug 637198 ***
Note You need to log in before you can comment on or make changes to this bug.