In nfs(5), the mountvers option is described as: The RPC version number used to contact the server's mountd. If this option is not specified, the client uses a version number appropriate to the requested NFS version. This option is useful when multiple NFS services are running on the same remote server host.
The question is, why are you specifying the *mount RPC version* instead of specifying the NFS protocol version and letting mount figure out the mountd version to use on its own? It's not that mount.nfs doesn't allow 'mountvers=n', it's that it doesn't want you to use mountvers=*2* here. Other values of 'n' work just fine, as does specifying an NFS protocol version with 'nfsvers=' instead. This probably is a bug (unless there happens to be some reason that mount version 2 has been deliberately disabled as insecure or dangerous?), but it looks to me like best practices would be to not use this option at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/251923 Title: /sbin/mount.nfs doesn't understand mount option mountvers=n -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
