Re: mount default minor version behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> On Nov 11, 2014, at 8:39 AM, Benjamin Coddington <bcodding@xxxxxxxxxx> wrote:
> 
> I will update mount.nfs so the default version is 4.1.

Hi Ben, can you explicitly test your change with NFSv4.0-only servers? Thanks!

> 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.
> 
> Ben
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux