[Bug 607039] Re: NFS4 automount using replicated servers doesn't work

[Stefan Bader]

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
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/607039

Title:
  NFS4 automount using replicated servers doesn't work

Status in “autofs5” package in Ubuntu:
  Fix Released
Status in “nfs-utils” package in Ubuntu:
  New

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/607039/+subscriptions