From: Michael Monnerie <lists.michael.monnerie@is.it-management.at>
To: linux-nfs@vger.kernel.org
Subject: How to make clients NOT block
Date: Sat, 16 Feb 2013 12:30:07 +0100 [thread overview]
Message-ID: <680509590.JPpPf8D3KZ@saturn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
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.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc | Tel: +43 660 415 6531
XING: https://www.xing.com/profile/Michael_Monnerie
Facebook: https://www.facebook.com/michael.monnerie
Twitter: @MichaelMonnerie https://twitter.com/MichaelMonnerie
LinkedIn: http://lnkd.in/uGx6ug
Google+: https://plus.google.com/u/0/100598203632716687928/
Protéger.at Internet Services Austria [gesprochen: Prot-e-schee]
http://protéger.at | http://proteger.at
Facebook: https://www.facebook.com/protegerat
Mitglied im it-management Netzwerk http://it-management.at
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2013-02-16 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 11:30 Michael Monnerie [this message]
2013-02-17 14:35 ` How to make clients NOT block Boaz Harrosh
2013-02-17 20:49 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=680509590.JPpPf8D3KZ@saturn \
--to=lists.michael.monnerie@is.it-management.at \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox