This needs to be reproduced and determined if it is resolved on the
current development version.
Thanks.
--
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:
NFS automount
** Changed in: autofs5 (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
--
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:
NFS automount using replicate
Cannot reproduce this on precise, at least (which has the same autofs
version as oneiric).
I used 3 hosts. Two had nfs-server installed, one had autofs4 and nfs-
client. The two nfs servers had a file /mnt/whoami ('master1' on one
and 'master2' on the other) and in /etc/exports had
/mnt 10
Reproduced on lucid (with -updates as well as with -proposed)
--
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:
NFS automount using replicated servers doesn't work
To ma
On natty, I don't get the 'connect(0.0.0.0)'. However, the mounts still
fail, and this time it is a bug in nfs. Even on an oneiric host, if I
do
mount -t nfs server:/mnt /mnt
I get back ENODEV from mount.nfs4.
On natty, if I switch /etc/auto.mnt to use nfs instead of nfs4, it
succeeds. I n
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: auto
I changed the title of this bug report from
NFS automount failover doesn't work
to
NFS automount using replicated servers doesn't work
as I believe it better reflects the problem and saying 'failover' in
combination with may put of the maintainers as autofs isn't supposed to
do real faillov