Bug#568194: I got bit by it
We have a heterogeneous network of systems here, including many
HP-UX 10.20 workstations, with a lot of NFS cross-mounting. After
upgrading a machine from lenny to squeeze, one of the very first
problems I encountered was that it failed to automount my home directory.
Eventually (with some suggestions from #debian@freenode) we traced it down
to an NFSv4 issue. Apparently when autofs attempts an NFS mount in
squeeze, it attempts an NFSv4 mount. And when it does this against an
HP-UX 10.20 NFS server, the result is a client that hangs for a few
minutes before finally failing (no, it does not seem to fall back to NFSv3
or anything else).
The configuration I had on the squeeze client *was* this:
arc3:~$ cat /etc/auto.master
#
# $Id: auto.master,v 1.4 2005/01/04 14:36:54 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc /etc/auto.misc --timeout=60
#/smb /etc/auto.smb
#/misc /etc/auto.misc
#/net /etc/auto.net
/nfs /etc/auto.net
In other words, just like it had been doing for the past several years,
it retrieved the auto.master map from NIS and used that to populate
the auto.home map which tells where everyone's home directories are.
arc3:~$ ypcat -k auto.master
/net/vol auto.vol -rw,hard,intr
/net/appl auto.appl -rw,hard,intr
/net/hosts -hosts -rw,hard,intr
/net/home auto.home -rw,hard,intr
But now in squeeze, apparently that is broken. I had to manually slurp
the auto.master map information into the /etc/auto.master file and
tweak it:
arc3:~$ cat /etc/auto.master
#
# $Id: auto.master,v 1.4 2005/01/04 14:36:54 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc /etc/auto.misc --timeout=60
#/smb /etc/auto.smb
#/misc /etc/auto.misc
#/net /etc/auto.net
/nfs /etc/auto.net
# Contents of auto.master map, then add mountvers=3
/net/vol auto.vol -rw,hard,intr,mountvers=3
/net/appl auto.appl -rw,hard,intr,mountvers=3
/net/hosts -hosts -rw,hard,intr,mountvers=3
/net/home auto.home -rw,hard,intr,mountvers=3
This suffices as a workaround, for us, but is this really the intent?
Also I agree with Nick Leverton that the documentation is wrong or at
least confusing. My initial diagonsis attempts began by comparing
the results of "mount -t nfs ..." and "mount -t nfs4 ..." because the
documentation said that these two options should give different behaviors.
But they do not.
Reply to: