From: Anna Schumaker <Anna.Schumaker@netapp.com>
To: Benjamin Coddington <bcodding@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: mount default minor version behavior
Date: Tue, 11 Nov 2014 10:27:27 -0500 [thread overview]
Message-ID: <54622ADF.4080807@Netapp.com> (raw)
In-Reply-To: <alpine.LRH.2.11.1411111017190.20279@sh-el6.eng.rdu2.redhat.com>
Hi Ben,
On 11/11/2014 10:20 AM, Benjamin Coddington wrote:
>
> On Tue, 11 Nov 2014, Trond Myklebust wrote:
>
>> Hi Ben,
>>
>> On Tue, Nov 11, 2014 at 9:39 AM, Benjamin Coddington
>> <bcodding@redhat.com> wrote:
>>> I will update mount.nfs so the default version is 4.1. I have two quick
>>> questions on desired behavior:
>>>
>>> o Should mounts that do not specify a minor version be upgraded to the
>>> default minor version?
>>>
>>> For example, should 'mount -overs=4' turn into 'mount -overs4.1', if the
>>> current default is 4.1?
>>>
>>>
>>> o If 'yes' to the above, should mount auto-retry decrementing minor
>>> versions if EPROTONOSUPPORT?
>>>
>>> For example, 'mount -overs=4' with a default of 4.2 would attempt: 4.2,
>>> then 4.1, then 4.0.
>>>
>> One thing you should note when doing this: the current parser for
>> /etc/nfsmount.conf does not support minor versions. I think it needs
>> to, so that we can continue to use it to set defaults.
>>
>> ...and to answer your questions above, I think that we should be able
>> to specify a 'default nfsv4 minor version' in /etc/nfsmount.conf, and
>> then negotiate down from there.
>> IOW: extend the 'Defaultvers' and 'Nfsvers' options to support 4.0,
>> 4.1, 4.2,....
> Ah, good idea to make it configurable.
>
>> The result should be that If I do 'mount -t nfs' with no '-overs'
>> option, then we start at 4.1 (if that is the default in
>> /etc/nfsmount.conf) and then try 4.0, 3, 2 in that order.
>> If I do 'mount -t nfs -overs=4', then again consult /etc/nfsmount.conf;
>> - if there is a default matching a v4 minor version, then start at
>> that and negotiate down (but stop at 4.0).
> Yep, those closely match the current behavior and that's what my first
> pass looks like.
>
>> - if there is no default in /etc/nfsmount.conf, then perhaps assume a
>> default of 0(????)
> That's the question, and I think it will be a very common case. Do we
> want to have an idea of a "best" minor version, and use that if no minor
> version is specified?
I don't think so. Right now users know that if they don't use a minor version then they'll be getting a v4.0 mount. I think we should keep this behavior so we don't accidentally break people's configuration.
Anna
>
> Ben
>
>> Cheers
>> Trond
>>
>>
>> --
>> Trond Myklebust
>>
>> Linux NFS client maintainer, PrimaryData
>>
>> trond.myklebust@primarydata.com
>>
> --
> 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
next prev parent reply other threads:[~2014-11-11 15:27 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 14:39 mount default minor version behavior Benjamin Coddington
2014-11-11 15:01 ` Weston Andros Adamson
2014-11-11 15:15 ` Benjamin Coddington
2014-11-11 15:01 ` Trond Myklebust
2014-11-11 15:20 ` Benjamin Coddington
2014-11-11 15:24 ` Trond Myklebust
2014-11-11 15:27 ` Anna Schumaker [this message]
2014-11-11 16:27 ` Boaz Harrosh
2014-11-11 19:19 ` Frank Filz
2014-11-11 19:25 ` Steve Dickson
2014-11-11 19:16 ` Steve Dickson
2014-11-11 20:43 ` Trond Myklebust
2014-11-12 13:08 ` Steve Dickson
2014-11-12 14:31 ` Trond Myklebust
2014-11-12 15:10 ` Steve Dickson
2014-11-12 15:28 ` Trond Myklebust
2014-11-12 15:37 ` Chuck Lever
2014-11-12 18:10 ` Steve Dickson
2014-11-12 18:41 ` Trond Myklebust
2014-11-12 20:07 ` J. Bruce Fields
2014-11-12 20:30 ` Steve Dickson
2014-11-12 20:17 ` Anna Schumaker
2014-11-12 20:32 ` Steve Dickson
2014-11-12 22:42 ` Trond Myklebust
2014-11-13 17:57 ` Steve Dickson
2014-11-13 18:52 ` Trond Myklebust
2014-11-13 19:02 ` J. Bruce Fields
2014-11-13 19:26 ` Trond Myklebust
2014-11-13 19:55 ` J. Bruce Fields
2014-11-13 20:22 ` Trond Myklebust
2014-11-13 20:38 ` J. Bruce Fields
2014-11-13 15:07 ` Chuck Lever
2014-11-13 20:31 ` Steve Dickson
2014-11-12 17:27 ` Steve Dickson
2014-11-11 16:38 ` Chuck Lever
2014-11-17 19:47 ` Benjamin Coddington
2014-11-17 21:02 ` Chuck Lever
2014-11-12 13:09 ` Benjamin Coddington
2014-11-12 14:36 ` Trond Myklebust
2014-11-12 15:01 ` Benjamin Coddington
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54622ADF.4080807@Netapp.com \
--to=anna.schumaker@netapp.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.