|
 |
5fd2c0 |
diff -up nfs-utils-1.3.0/utils/exportfs/exports.man.orig nfs-utils-1.3.0/utils/exportfs/exports.man
|
|
|
5fd2c0 |
--- nfs-utils-1.3.0/utils/exportfs/exports.man.orig 2017-11-03 07:45:47.000000000 -0400
|
|
|
5fd2c0 |
+++ nfs-utils-1.3.0/utils/exportfs/exports.man 2017-11-03 09:25:47.000000000 -0400
|
|
|
5fd2c0 |
@@ -410,7 +410,7 @@ of the filesystem must be handled elsewh
|
|
|
5fd2c0 |
|
|
|
5fd2c0 |
.TP
|
|
|
5fd2c0 |
.IR pnfs
|
|
|
5fd2c0 |
-This option allows enables the use of pNFS extension if protocol level
|
|
|
5fd2c0 |
+This option enables the use of the pNFS extension if the protocol level
|
|
|
5fd2c0 |
is NFSv4.1 or higher, and the filesystem supports pNFS exports. With
|
|
|
5fd2c0 |
pNFS clients can bypass the server and perform I/O directly to storage
|
|
|
5fd2c0 |
devices. The default can be explicitly requested with the
|
|
|
5fd2c0 |
diff -up nfs-utils-1.3.0/utils/mount/nfs.man.orig nfs-utils-1.3.0/utils/mount/nfs.man
|
|
|
5fd2c0 |
--- nfs-utils-1.3.0/utils/mount/nfs.man.orig 2017-11-03 07:45:47.000000000 -0400
|
|
|
5fd2c0 |
+++ nfs-utils-1.3.0/utils/mount/nfs.man 2017-11-03 09:23:20.000000000 -0400
|
|
|
5fd2c0 |
@@ -11,11 +11,8 @@ NFS is an Internet Standard protocol
|
|
|
5fd2c0 |
created by Sun Microsystems in 1984. NFS was developed
|
|
|
5fd2c0 |
to allow file sharing between systems residing
|
|
|
5fd2c0 |
on a local area network.
|
|
|
5fd2c0 |
-The Linux NFS client supports three versions
|
|
|
5fd2c0 |
-of the NFS protocol:
|
|
|
5fd2c0 |
-NFS version 2 [RFC1094],
|
|
|
5fd2c0 |
-NFS version 3 [RFC1813],
|
|
|
5fd2c0 |
-and NFS version 4 [RFC3530].
|
|
|
5fd2c0 |
+Depending on kernel configuration, the Linux NFS client may
|
|
|
5fd2c0 |
+support NFS versions 2, 3, 4.0, 4.1, or 4.2.
|
|
|
5fd2c0 |
.P
|
|
|
5fd2c0 |
The
|
|
|
5fd2c0 |
.BR mount (8)
|
|
|
5fd2c0 |
@@ -88,9 +85,8 @@ These options are valid to use with any
|
|
|
5fd2c0 |
The NFS protocol version number used to contact the server's NFS service.
|
|
|
5fd2c0 |
If the server does not support the requested version, the mount request
|
|
|
5fd2c0 |
fails.
|
|
|
5fd2c0 |
-If this option is not specified, the client negotiates a suitable version
|
|
|
5fd2c0 |
-with
|
|
|
5fd2c0 |
-the server, trying version 4 first, version 3 second, and version 2 last.
|
|
|
5fd2c0 |
+If this option is not specified, the client tries version 4.1 first,
|
|
|
5fd2c0 |
+then negotiates down until it finds a version supported by the server.
|
|
|
5fd2c0 |
.TP 1.5i
|
|
|
5fd2c0 |
.BI vers= n
|
|
|
5fd2c0 |
This option is an alternative to the
|
|
|
5fd2c0 |
@@ -752,7 +748,7 @@ NOTE: When used together, the 'local_loc
|
|
|
5fd2c0 |
by 'nolock'/'lock' mount option.
|
|
|
5fd2c0 |
.SS "Options for NFS version 4 only"
|
|
|
5fd2c0 |
Use these options, along with the options in the first subsection above,
|
|
|
5fd2c0 |
-for NFS version 4 and newer.
|
|
|
5fd2c0 |
+for NFS version 4.0 and newer.
|
|
|
5fd2c0 |
.TP 1.5i
|
|
|
5fd2c0 |
.BI proto= netid
|
|
|
5fd2c0 |
The
|
|
|
5fd2c0 |
@@ -825,7 +821,7 @@ the behavior of this option in more deta
|
|
|
5fd2c0 |
Specifies a single IPv4 address (in dotted-quad form),
|
|
|
5fd2c0 |
or a non-link-local IPv6 address,
|
|
|
5fd2c0 |
that the NFS client advertises to allow servers
|
|
|
5fd2c0 |
-to perform NFS version 4 callback requests against
|
|
|
5fd2c0 |
+to perform NFS version 4.0 callback requests against
|
|
|
5fd2c0 |
files on this mount point. If the server is unable to
|
|
|
5fd2c0 |
establish callback connections to clients, performance
|
|
|
5fd2c0 |
may degrade, or accesses to files may temporarily hang.
|
|
|
5fd2c0 |
@@ -838,6 +834,11 @@ In the presence of multiple client netwo
|
|
|
5fd2c0 |
special routing policies,
|
|
|
5fd2c0 |
or atypical network topologies,
|
|
|
5fd2c0 |
the exact address to use for callbacks may be nontrivial to determine.
|
|
|
5fd2c0 |
+.IP
|
|
|
5fd2c0 |
+NFS protocol versions 4.1 and 4.2 use the client-established
|
|
|
5fd2c0 |
+TCP connection for callback requests, so do not require the server to
|
|
|
5fd2c0 |
+connect to the client. This option is therefore only affect NFS version
|
|
|
5fd2c0 |
+4.0 mounts.
|
|
|
5fd2c0 |
.TP 1.5i
|
|
|
5fd2c0 |
.BR migration " / " nomigration
|
|
|
5fd2c0 |
Selects whether the client uses an identification string that is compatible
|
|
|
5fd2c0 |
@@ -1726,7 +1727,7 @@ file system table
|
|
|
5fd2c0 |
.TP 1.5i
|
|
|
5fd2c0 |
.I /etc/nfsmount.conf
|
|
|
5fd2c0 |
Configuration file for NFS mounts
|
|
|
5fd2c0 |
-.SH BUGS
|
|
|
5fd2c0 |
+.SH NOTES
|
|
|
5fd2c0 |
Before 2.4.7, the Linux NFS client did not support NFS over TCP.
|
|
|
5fd2c0 |
.P
|
|
|
5fd2c0 |
Before 2.4.20, the Linux NFS client used a heuristic
|
|
|
5fd2c0 |
@@ -1745,9 +1746,9 @@ when the
|
|
|
5fd2c0 |
.BR rsize " and " wsize
|
|
|
5fd2c0 |
settings were smaller than the system's page size.
|
|
|
5fd2c0 |
.P
|
|
|
5fd2c0 |
-The Linux NFS client does not yet support
|
|
|
5fd2c0 |
-certain optional features of the NFS version 4 protocol,
|
|
|
5fd2c0 |
-such as security negotiation, server referrals, and named attributes.
|
|
|
5fd2c0 |
+The Linux client's support for protocol versions depend on whether the
|
|
|
5fd2c0 |
+kernel was built with options CONFIG_NFS_V2, CONFIG_NFS_V3,
|
|
|
5fd2c0 |
+CONFIG_NFS_V4, CONFIG_NFS_V4_1, and CONFIG_NFS_V4_2.
|
|
|
5fd2c0 |
.SH "SEE ALSO"
|
|
|
5fd2c0 |
.BR fstab (5),
|
|
|
5fd2c0 |
.BR mount (8),
|
|
|
5fd2c0 |
@@ -1780,4 +1781,8 @@ RFC 1833 for the RPC bind specification.
|
|
|
5fd2c0 |
.br
|
|
|
5fd2c0 |
RFC 2203 for the RPCSEC GSS API protocol specification.
|
|
|
5fd2c0 |
.br
|
|
|
5fd2c0 |
-RFC 3530 for the NFS version 4 specification.
|
|
|
5fd2c0 |
+RFC 7530 for the NFS version 4.0 specification.
|
|
|
5fd2c0 |
+.br
|
|
|
5fd2c0 |
+RFC 5661 for the NFS version 4.1 specification.
|
|
|
5fd2c0 |
+.br
|
|
|
5fd2c0 |
+RFC 7862 for the NFS version 4.2 specification.
|