Date: Fri, 7 Jan 2011 09:56:31 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: grarpamp <grarpamp@gmail.com> Subject: Re: NFS - DNS fail stops boot in mountlate Message-ID: <201101070956.31374.jhb@freebsd.org> In-Reply-To: <AANLkTimeRfTO4RT0M5%2Bx28OGM0cCXTMY=VADR1ZEdKeW@mail.gmail.com> References: <AANLkTimeRfTO4RT0M5%2Bx28OGM0cCXTMY=VADR1ZEdKeW@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, January 06, 2011 2:26:10 pm grarpamp wrote: > RELENG_8. > > ### 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 out > mount_nfs: Cannot immediately mount 192.168.0.10:/tmp, backgrounding > /dev/ad0s1a on / (ufs, local, read-only, fsid <snip1>) > 0 > > [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. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101070956.31374.jhb>