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.] mount -v foo:/tmp ; echo $? mount_nfs: foo: hostname nor servname provided, or not known /dev/ad0s1a on / (ufs, local, read-only, fsid <snip1>) 1 [drops to shell, which is obviously bad behaviour.] [mount_nfs should background as in the former.]
It's generally better to post a description of your problem, rather than copy and pasting command line examples. What makes perfect sense to you may (or even probably does) not make sense to others. :) Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
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: Timedout> 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