On Tue, 2012-02-07 at 18:30 +0000, Adamson, Dros wrote:
> On Feb 7, 2012, at 1:21 PM, Boaz Harrosh wrote:
>
> > On 02/07/2012 06:59 PM, Chuck Lever wrote:
> >> Hi-
> >>
> >> On Feb 7, 2012, at 11:49 AM, Weston Andros Adamson wrote:
> >>>
> >>> NFS: add mount options 'v4.0' and 'v4.1'
> >
> > Good god thanks, that'll be nice.
> >
> > Why did we have to suffer for 5 years without it? ;-)
> >
> >>> Signed-off-by: Weston Andros Adamson <dros@xxxxxxxxxx>
> >>> ---
> >>> Updated to add 'v4.0' as trond requested.
> >>>
> >>> We'll talk about this change at connectathon.
> >>>
> >>> This 'just works' with mount.nfs(8) -- v.* options are passed to the
> >>> kernel with no modifications needed.
> >>
> >> I'm more concerned about version auto-negotation.
> >>
> >
> > If we are at it can we also have a "this-version-only" option which
> > disables "auto-negotation"
>
> Trond seems to have a plan for this. I'll defer to him.
That's a longer term effort. I don't think we need to care until we're
ready to take NFSv4.1 out of EXPERIMENTAL status.
That said, I see the 'vers=4' being reserved for auto-negotiation of
minor version, and the 'vers=4.x' as requiring a specific minor version
number.
The way auto-negotiation is supposed to work is laid out in
RFC3530(-bis): the client attempts the largest minor version that it
supports, and the server replies with an OK, or a MINOR_VERSION_MISMATCH
depending on whether it supports that minor version or not. If not, the
client retries with the next largest minor version, .... rince, repeat
until successful...
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
��.n��������+%������w��{.n�����{��w��� jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
