*** 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 =
** 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
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
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
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.
@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.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
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
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
