https://bugzilla.novell.com/show_bug.cgi?id=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c21 --- Comment #21 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-20 17:59:18 UTC --- Ok, tried as Neil suggested / *(rw,insecure,no_root_squash,sync,no_subtree_check) /bak *(rw,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) instead of my original operating config /srv/export *(bind=/,rw,fsid=0,insecure,no_root_squash,sync,no_subtree_check) /srv/export/bak *(bind=/bak,rw,nohide,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) in /etc/exportfs . As you may notice, in my original config the third entry is an nfs3 export since systemrescuecd linux cannot boot over nfs4. However, the both first entries as nfs 4, as they contain fsid and or bind. The docu http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n... says (what is imho correct):
NFSv3 and NFSv4 exports can coexist on a server. After enabling the support for NFSv4 in the initial configuration dialog, those exports for which fsid=0 and bind=/target/path are not included in the option list are considered v3 exports.
Thus the suggested config at the top only exports via nfs3, ie, 'mount -o vers=4 server:/bak /mnt' or 'mount server:/bak /mnt' fail, ie, they hang for at least 5 minutes! Although both should automatically fall back to nfs3, as man nfs tells:
nfsvers=n The NFS protocol version number used to contact the server's NFS service. If the server does not support the requested version, the mount request fails. If this option is not specified, the client negotiates a suit- able version with the server, trying version 4 first, version 3 second, and version 2 last.
It is very likely that Neil's test was over nfs3. In /etc/sysconfig/nfs I have set USE_KERNEL_NFSD_NUMBER="4" NFS3_SERVER_Support="yes" which should be correct, but maybe that is of interest. For the suggested version: Executing 'mount -o nfsvers=3 server:/ /mnt' logs
2013-03-20T18:50:29.576808+01:00 server rpc.mountd[8598]: Cannot export /, possibly unsupported filesystem or fsid= required in the clients /var/log/messages
A further reason pro bind=... . Under /bak I have a different file system mounted as under /, ie, a partition on another hard disk. Using my configuration makes it possible on the client with a simple 'mount server:/ /mnt' to have full access to /mnt/bak = /bak on the server. Please note that the provided examples are a simplifies version of my server config, eg, I use Kerberos. If you are asking me, bind= is useful and necessary in the current situation. It should not be deprecated. The only option I see is to use bind-mounts within /etc/fstab, which will always be present even if the nfsserver is not running, however. @Neil: What is your advice? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.