Doh! I think I found out what it going on... The problem can be, as it has been said before, reduced to attempting a NFS mount with:
mount -tnfs4 <server>:<path> <mntpt> which will fail with a completely useless message of no such device. It was also said that -tnfs does work. Now the interesting thing is that *after* one successful run with -tnfs, the -tnfs4 does *also* work. I must admit it took me a while to think of module loading. But that was the solution in my tests. Apparently a mount -tnfs automatically loads the nfs module, which does not work for -tnfs4 (I guess because there is some glue missing to tell the system that the nfs module is the correct one for both). Could those affected try a quick work-around, please? Create a new file name /etc/modprobe.d/nfs4.conf with the following content: alias nfs4 nfs In theory this should make sure the module gets autoloaded and the nfs4 autofs setup should be working... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/607039 Title: NFS4 automount using replicated servers doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/607039/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
