On Sun, Feb 1, 2015 at 4:18 PM, walt w41...@gmail.com wrote:
Everybody's favoritest cuddly FOSS personality Theo de Raadt is quoted in
Wikipedia as saying: NFS4 is not on our roadmap. It's a horribly bloated
protocol that they keep adding crap to.
The latest nfs-utils package demonstrates why he's annoyed with NFS4:
This morning I got this when mounting an nfs share that's been working for
many months:
#mount.nfs -v a6:/usr/portage /usr/portage/
mount.nfs: timeout set for Sun Feb 1 13:09:39 2015
mount.nfs: trying text-based options
'vers=4.2,addr=192.168.1.84,clientaddr=192.168.1.84'
mount.nfs: mount(2): Invalid argument
mount.nfs: an incorrect mount option was specified
Note the vers=4.2, which is brand new behavior. My kernel doesn't have
any config option for nfs-4.2 because I've never enabled nfs-4.1 and the
4.2 option is invisible in menuconfig without it. Who knew?
So, you either need to enable nfs-4.1 *and* nfs-4.2 in your kernel, or start
using the nfsvers=4 mount option in fstab.
Anyone got an opinion on the need for nfs-4.2? Is it better, or just newer?
I was happy with nfs3 until it stopped working for reasons I still don't
understand :(
I've been setting -o nfsvers=vers systematically ever since nfsv4
was released... :(
You can use /etc/nfsmount.conf to control the behavior of mount.nfs{,4}.
Do you have net-fs/nfs-utils nfsv41 in package.use? In the eix
output below, nfs-utils is compiled with -nfsv41 by default:
# eix nfs-utils
[I] net-fs/nfs-utils
Available versions: 1.2.9-r3^t ~1.3.0-r1^t 1.3.1-r1^t
~1.3.2-r1^t {caps ipv6 kerberos +libmount nfsdcld +nfsidmap +nfsv4
nfsv41 selinux tcpd +uuid}
Installed versions: 1.3.1-r1^t(10:47:45 AM 01/27/2015)(libmount
nfsidmap nfsv4 uuid -caps -ipv6 -kerberos -nfsdcld -nfsv41 -selinux
-tcpd)
Homepage:http://linux-nfs.org/
Description: NFS client and server daemons
Should mount.nfs4 try an nfs4.1 mount if nfs-utils is compiled with
-nfsv41? Or is the use flag intended for rpc.nfsd only?
