7 messages in org.freebsd.freebsd-hackersNFS server not responding prevents boot| From | Sent On | Attachments |
|---|---|---|
| Steven Hartland | May 19, 2006 12:37 am | |
| Steven Hartland | May 19, 2006 12:47 am | |
| Mike Meyer | May 19, 2006 2:33 am | |
| Sergey Babkin | May 19, 2006 11:30 am | |
| Steven Hartland | May 19, 2006 1:17 pm | |
| Chuck Lever | May 19, 2006 2:04 pm | |
| Kip Macy | May 20, 2006 7:57 pm |
| Subject: | NFS server not responding prevents boot | |
|---|---|---|
| From: | Chuck Lever (ce...@citi.umich.edu) | |
| Date: | May 19, 2006 2:04:03 pm | |
| List: | org.freebsd.freebsd-hackers | |
Sergey Babkin wrote:
From: Steven Hartland <kill...@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