Red Hat Bugzilla – Bug 510234
Document which options are shared and which are not when mounting multiple volumes from the same server
Last modified: 2009-10-13 11:15:38 EDT
Description of problem:
The addition of the nosharecache option allows an admin to force the mounting of the same volume more than once with different options, but even then some options are bound to the internal NFS client for that server and cannot be changed. For example, on RHEL-5.3 it seems timeo, bg and proto are not changed in mounts after the first one. It is important that the manpage documents what really is shared by multiple mounts and what is not.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
# mount -o udp,nosharecache server:/export/nfs /mnt1
# mount -o tcp,nosharecache,timeo=123,rsize=8192,wsize=8192,soft server:/export/nfs /mnt2
# grep server /proc/mounts
server:/export/nfs /mnt1 nfs rw,vers=3,rsize=32768,wsize=32768,hard,nosharecache,proto=udp,timeo=11,retrans=2,sec=sys,addr=server 0 0
server:/export/nfs /mnt2 nfs rw,vers=3,rsize=8192,wsize=8192,soft,nosharecache,proto=udp,timeo=11,retrans=2,sec=sys,addr=server 0 0
Notice proto, timeo.
Documentation states correctly what is always shared and what is not, so that an admin can know what to expect.
The transport protocol sharing is a bug. See RH bz#460659.
*** This bug has been marked as a duplicate of bug 460659 ***