Date: Fri, 19 May 2006 10:04:15 -0400 From: Chuck Lever <cel@citi.umich.edu> To: babkin@users.sf.net Cc: freebsd-hackers@freebsd.org, Steven Hartland <killing@multiplay.co.uk> Subject: Re: NFS server not responding prevents boot Message-ID: <446DD05F.6070304@citi.umich.edu> In-Reply-To: <18923565.8854391148037026048.JavaMail.root@vms168.mailsrvcs.net> References: <18923565.8854391148037026048.JavaMail.root@vms168.mailsrvcs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Sergey Babkin wrote: >> From: Steven Hartland <killing@multiplay.co.uk> > >>> Anyway the big question is how can I change all our NFS >>> mounts so that failed mounts dont prevent the machines >>> booting to the point where they can be fixed remotely >>> i.e. have started sshd. >> Doh!! spent ages googling for the answer then found it >> in 2mins of looking through the man pages. >> >> The option for anyone interested is "bg" for -b from >> the command line to mount: >> [quote="man mount_nfs"] >> -b >> If an initial attempt to contact the server fails, fork off a > > I usually use "soft,bg". The "soft" option makes the > operations on this filesystem fail if the server > is not available instead of hanging (unkillable!) > forever and waiting for the server to come up. "soft" is usually a bad idea if you care about data integrity. It can cause all kinds of silent data corruption. Even on read-only mounts, a soft timeout can cause clients to corrupt their own caches. If you absolutely must use "soft", then also use NFS over TCP, and use a long retransmit timeout (like 60 seconds) and enable the dumb timer (the "-d") option. That's about the safest way to use "soft". -- corporate: cel at netapp dot com personal: chucklever at bigfoot dot com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?446DD05F.6070304>