[PATCH 0/3] : mount.nfs: Try v4 mounts first (Release 4)

Chuck Lever chuck.lever at oracle.com
Tue Sep 29 15:25:35 EDT 2009


On Sep 29, 2009, at 3:20 PM, Trond Myklebust wrote:

> On Tue, 2009-09-29 at 15:10 -0400, Chuck Lever wrote:
>> On Sep 29, 2009, at 9:12 AM, Steve Dickson wrote:
>>
>>> On 09/28/2009 04:18 PM, Chuck Lever wrote:
>>>> What happens when you try your version of mount.nfs on an older
>>>> kernel
>>>> version that does not support "-t nfs -o v4" ?
>>> The mount fails with "mount.nfs: an incorrect mount option was
>>> specified"
>>> This this is expected...
>>
>> Not expected if mount.nfs going to try v4 first when the user didn't
>> specify an NFS version.  Your proposal tacks on ",v4" when it tries
>> mounting with NFSv4, right?
>>
>> In other words, mount.nfs can't try v4 first unless the kernel
>> supports "-t nfs -o v4".
>
> Please use the industry-standard, which is "-overs=4", rather than  
> Linux
> specific shorthands like '-ov4'.
>
> That also makes it consistent with what /proc/self/mountinfo will
> display...

Sounds reasonable.  I hadn't thought of that, but it looks like my  
version of the patches does send down "vers=4" in this case.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





More information about the NFSv4 mailing list