The problem does not appear on Fedora using autofs 5.0.5 so it looks
like this is an Ubuntu specific bug.
Please note that the description for this bug report is misleading as
autofs doesn't do failover (as far as I know). However it is supposed
to be able to automaticaly choose an available serv
I just verified the problem still exists on Maverick running autofs5
5.0.5-0ubuntu2.
Same scenario: if I list only 1 server the automount works fine, if I
add a second server the mount fails completely without leaving any logs.
--
You received this bug notification because you are a member of Ub
I'm having the same issue using autofs 5.0.4-3.1ubuntu5.1 on lucid.
When using NFS3 specifying replicated servers does work, when using NFS4 it
doesn't. If I run automount manually with verbose and debugging enabled I see
the
following output when trying to access /usr/local:
#
** Changed in: autofs5 (Ubuntu)
Importance: Undecided => Medium
--
NFS automount failover doesn't work
https://bugs.launchpad.net/bugs/607039
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu.
--
Ubuntu-server-bugs mai
** Attachment added: "/etc/autofs.d/auto.vcs that the auto.master file refers
to"
http://launchpadlibrarian.net/52140619/auto.vcs
--
NFS automount failover doesn't work
https://bugs.launchpad.net/bugs/607039
You received this bug notification because you are a member of Ubuntu
Server Team, w
** Attachment added: "auto.master file"
http://launchpadlibrarian.net/52140589/auto.master
--
NFS automount failover doesn't work
https://bugs.launchpad.net/bugs/607039
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu.
** Attachment added: "strace output"
http://launchpadlibrarian.net/52140531/strace-autofs-and-kids.txt
--
NFS automount failover doesn't work
https://bugs.launchpad.net/bugs/607039
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs
