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

[Serge Hallyn]

I was wrong!  In fact using nfs in place of nfs4 does work on lucid.

So I believe this can all be blamed on nfs4 failure on lucid through
oneiric.

** Summary changed:

- NFS automount using replicated servers doesn't work
+ NFS4 automount using replicated servers doesn't work

** Changed in: autofs5 (Ubuntu)
     Assignee: Serge Hallyn (serge-hallyn) => (unassigned)

** Changed in: autofs5 (Ubuntu)
       Status: New => Fix Released

** Also affects: nfs-utils (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: nfs-utils (Ubuntu)
   Importance: Undecided => Medium

** Description changed:

  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