[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
*** This bug is a duplicate of bug 662711 *** https://bugs.launchpad.net/bugs/662711 This is actually fixed in Precise by a change to nfs-utils for bug #662711. For that reason I'll mark the bug report here as a duplicate. ** Changed in: module-init-tools (Ubuntu) Status: New = Invalid ** This bug has been marked a duplicate of bug 662711 idmap should be started by default because mount.nfs now negotiates NFSv4 before NFSv3 -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
** Also affects: module-init-tools (Ubuntu) Importance: Undecided Status: New ** Description changed: + module-init-tools in debian has 'alias nfs4 nfs' in + /etc/modprobe.d/aliases.conf. ubuntu does not have that file or that + line. We need it because nfs4.ko no longer exists, but 'mount -t nfs4' + tries to load it. + Binary package hint: autofs5 [ updated description: mount -t nfs4 server:/mnt /mnt fails through oneiric with -ENODEV from mount.nfs4 ] In lucid, using autofs5 version 5.0.4-3.1ubuntu5, we are having trouble using failover with NFS. Autofs allows you to specify multiple hosts with weighting in its configuration files and will fall back to a secondary host if the first host is not available at mount time. However, currently on our systems, the mount fails completely. This functionality does work with our RHEL 5 hosts (which use autofs 5.0.1). Automounting from a single host does work, but when we supply multiple hosts, an strace shows that it's trying to connect to the IP address '0.0.0.0', port 0, rather than any of the hosts we specify. I have attached the full strace output, our /etc/auto.master file, and the relevant file from /etc/autofs.d including the multiple hosts. -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
I carefully went through the various man pages again and found that despite me missing those before, there are indications: man nfs ... The fstype field contains nfs. Use of the nfs4 fstype in /etc/fstab is deprecated. ... To mount using NFS version 4, use either the nfs file system type, with the nfsvers=4 mount option, or the nfs4 file system type. man mount.nfs4 ... Under Linux 2.6.32 and later kernel versions, mount.nfs can mount all NFS file system versions. Under earlier Linux kernel versions, mount.nfs4 must be used for mounting NFSv4 file systems while mount.nfs must be used for NFSv3 and v2. The man page for mount mentions nfs4 but says nothing specific about nfs4 but mentions it. And the examples in nfs(5) rather show the nfs4 fstype approach. So it is a bit mixed. My feeling would be that the nfs related man pages may be a bit more actively pushing people to drop nfs4 as the fstype. But probably add an alias definition in modprobe.d (if that is allowed by policy). Steve, this sounds to me like we should open a related debian bug along. Or would we make changes in our package an then ask for things to be picked up? -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
So as expected upstream was not too exited about a change to the kernel module. In fact the answer was suggesting that using the fstype nfs4 is rather deprecated. And I was observing that even using mount -tnfs ... the resulting mount options which could be observed in cat /proc/mounts were the same as using nfs4. Unfortunately the man pages for mount (and probably other too) do not reflect this at all. -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
I am not sure whether mount.nfs4 ever did load the right module. At least it does not do it back to Lucid and I have not checked farther back. It may be that nfs once was built in and thus avoided all the issues. The modprobe call happens in mount. Which takes the fstype as the module to load. So I think the way forward is either /etc/modprobe.d alias definition or having the module itself declare that alias. I'll try to suggest the latter but I am not sure how acceptable that is upstream. The alias is simpler, but question would be which package this should go into. -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
@Steve, this seems actually already to be addressed. Unfortunately in a way that is easy to get wrong. The nfs module would for example be autoloaded when the idmapd gets started. And the /etc/default/nfs-common comments clearly say it should be needed for v4. However one seems to be able to get a mount done without it being set to yes. (Probably running into other issues later). It would be good if there would be a way to get those things right in a simpler way. But I cannot think of a good one right now. Should mount.nfs4 start required daemons? But then that may miss sensible configuration... -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
mount.ntfs4 certainly shouldn't start any daemons, but I would expect it to autoload the nfs4 module the same way it previously autoloaded the nfs module. BTW, for 12.04 we always start idmapd automatically; but if using autofs, it's still not guaranteed that idmapd will have started before autofs starts. -- 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
[Bug 607039] Re: NFS4 automount using replicated servers doesn't work
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
Re: [Bug 607039] Re: NFS4 automount using replicated servers doesn't work
On Wed, Nov 23, 2011 at 01:48:24PM -, Stefan Bader wrote: 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. Note that this is upstream bug #117957, which has been reported some time ago. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 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
