-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 В Thu, 11 Jul 2013 14:54:52 +0200 (CEST) "Carlos E. R." <carlos.e.r@opensuse.org> пишет:
So obviously, nfs4 fails. Why is the system attempting to use nfs4, then, if the fstab entry does not say "nfs4"?
There is no "nfs4" filesystem. There is only one nfs client implementation that supports NFS V2, V3, V4. mount.nfs and mount.nfs4 are exactly the same programs: bor@opensuse:~> LC_ALL=C ll /sbin/mount.nfs* - -rwsr-xr-x 1 root root 110888 Jun 18 16:49 /sbin/mount.nfs lrwxrwxrwx 1 root root 9 Jun 21 06:12 /sbin/mount.nfs4 -> mount.nfs with only difference (at least, in the past) being NFS protocol version used.
Can I somehow specify nfs3?
Of course. mount -o nfsvers=3 ... It is always good practice to specify required NFS version explicitly. It is not the first time version and defaults change (NFS V2 => NFS V3).
I tried to write "nfs3" in fstab, got an error that said nfs3 was invalid or something.
Right, see above. By default client should negotiate NFS version, depending on which one is supported by server. So leaving explicit version will result in different behavior depending on what client/server combination support. As NFS V3 and NFS V4 have completely different models for sharing and user mappings you usually cannot simply drop in NFS V4 in place of NFS V3 and expect it to work. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlHiXK4ACgkQR6LMutpd94xqtgCfU6fUfzswJHGMZy68y9oy3gpD kyAAoIRQX7u7cs2WGe29j9W4NpqUT6LI =sK/0 -----END PGP SIGNATURE-----