The nfs-kernel-server init script runs
rpcinfo -u localhost nfs 3
if localhost cannot be resolved for some reason this command will fail,
and the server is started with the option
--no-nfs-version 3
even though the kernel could actually support this version.
rpcinfo looks up localhost as specified in nsswitch.conf, and if one has
the latter configured as the man page suggests, namely
hosts: dns [!UNAVAIL=return] files
the lookup of localhost will fail.
If NFS v3 is not available, and you have not configured NFS v4, then the
clients will negotiate NFS v2 or v1, and these have no acl support. If
the clients try to mount using version 4, the mount will fail.
I close the bug as resolved.
** Changed in: nfs-utils (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nfs-utils (Ubuntu)
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/911796
Title:
NFS clients can no longer mount shares
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/911796/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
