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

Steve Langasek steve.langasek at canonical.com
Wed Nov 23 17:33:23 UTC 2011


On Wed, Nov 23, 2011 at 01:48:24PM -0000, 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 Developer                                    http://www.debian.org/
slangasek at ubuntu.com                                     vorlon at debian.org

-- 
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




More information about the foundations-bugs mailing list