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

Serge Hallyn 607039 at bugs.launchpad.net
Tue Dec 13 22:07:13 UTC 2011


** 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
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 “module-init-tools” package in Ubuntu:
  New
Status in “nfs-utils” package in Ubuntu:
  New

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

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