Re: [PATCH] nfsman: document minorversion

[NeilBrown <neilb@suse.com>]

[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]

On Thu, Sep 07 2017, Jianhong.Yin wrote:

> Signed-off-by: Jianhong Yin <yin-jianhong@163.com>
> ---
>  utils/mount/nfs.man | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
>
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index cc6e992..7d42f19 100644
> --- a/utils/mount/nfs.man
> +++ b/utils/mount/nfs.man
> @@ -779,6 +779,23 @@ so if this mount option is not specified, the NFS version 4 client
>  uses the TCP protocol.
>  Refer to the TRANSPORT METHODS section for more details.
>  .TP 1.5i
> +.BI minorversion= n
> +Specifies the protocol minor version number.
> +NFSv4 introduces "minor versioning," where NFS protocol enhancements can
> +be introduced without bumping the NFS protocol version number.
> +Before kernel 2.6.38, the minor version is always zero, and this
> +option is not recognized.
> +After this kernel, specifying "minorversion=1" enables a number of
> +advanced features, such as NFSv4 sessions.

This is not quite correct.  nfs-utils now defaults to the most recent
version of NFS that is supported by the kernel.  So if your kernel
supports v4.2, then specifying "minorversion=1" *disables* some features.

NeilBrown


> +.IP
> +Recent kernels allow the minor version to be specified using the
> +.B vers=
> +option.
> +For example, specifying
> +.B vers=4.1
> +is the same as specifying
> +.BR vers=4,minorversion=1 .
> +.TP 1.5i
>  .BI port= n
>  The numeric value of the server's NFS service port.
>  If the server's NFS service is not available on the specified port,
> -- 
> 2.13.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]