On 02/16/2013 01:30 PM, Michael Monnerie wrote:
> Dear list,
>
> we've had several servers block today because they all have a NFS mount point
> from a linux kernel 3.7.6 server. This is the fstab entry:
>
> 1.1.1.1:/nfsshare/all /shared nfs4 defaults,tcp,intr,relatime,async,acl 0 9
>
> The NFS server crashed and was offline, that made all clients block. Even
> after the NFS server was up again, most clients were stuck to the point they
> had to be rebooted. What mount options should we use so clients don't block
> completely when the NFS server is gone? It's no problem to unmount the NFS
> share, or get errors, but the clients must not stop their work.
>
It's the "-o soft" mount option to mount or fstab. Note that it will unstuck
you at most operations, after a timeout the Applications will receive EIO.
("most", because rarely it'll D state anyway)
Cheers
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
