NFS - DNS fail stops boot in mountlate
jhb at freebsd.org
Fri Jan 7 15:03:35 UTC 2011
On Thursday, January 06, 2011 2:26:10 pm grarpamp wrote:
> ### setup
> mount -d -a -l -v -t nfs
> exec: mount_nfs -o ro -o tcp -o bg -o nolockd -o intr 192.168.0.10:/tmp /mnt
> exec: mount_nfs -o ro -o tcp -o bg -o nolockd -o intr foo:/tmp /mnt
> 192.168.0.10 has been unplugged, no arp entry.
> Host foo not found: 3(NXDOMAIN)
> ### result
> mount -v 192.168.0.10:/tmp ; echo $?
> [tcp] 192.168.0.10:/tmp: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed
> mount_nfs: Cannot immediately mount 192.168.0.10:/tmp, backgrounding
> /dev/ad0s1a on / (ufs, local, read-only, fsid <snip1>)
> [this is ok.]
I've seen a regression in 8 at work where NFS mounts seem to fail on DNS on
every boot (we have a small number of mounts, < 10) whereas 7 worked fine on
every boot. I haven't tracked it down yet, but 8 is certainly more fragile
than 7 for mounting NFS on boot.
More information about the freebsd-stable