Comment 7 for bug 680680

Revision history for this message
Christian Mudra (brixlwupf) wrote :

Following the above hint from Peter Bell, I've now added the proto and vers options to the amd.home-map (beside that, I set the rsize and wsize to 16k). Demanded are the following options:

~$ ypcat -k amd.home | grep 'default '
/defaults type:=nfs;sublink=${key};opts:=rw,grpid,hard,intr,nodevs,nosuid,vers=3,proto=tcp,rsize=16384,wsize=16384;rfs:=${autodir}/${rhost}/fs1/home;fs:=${autodir}/${rhost}/fs1/home

The result is:

~$ cat /proc/mounts | grep nfs | grep home
seth:(pid1512,port1022)/ /home nfs rw,relatime,vers=2,rsize=1024,wsize=1024,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=none,addr=127.0.0.1 0 0
amun:/net/amun/fs1/home/ /net/amun/fs1/home nfs rw,nosuid,relatime,vers=2,rsize=8192,wsize=8192,namlen=255,acregmin=0,acregmax=0,acdirmin=0,acdirmax=0,hard,proto=udp,port=65535,timeo=7,retrans=3,sec=sys,local_lock=none,addr=172.20.91.20 0 0

The amd registers in the mount tab with vers=2,proto=udp,rsize=1024,wsize=1024, while the mount itself is mounted with vers=2,proto=udp, rsize=8192,wsize=8192.
The given workaround does not work for me, and I also don't have a clue why the 16k read/write size is also not used.