From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michael Monnerie <lists.michael.monnerie@is.it-management.at>
Cc: linux-nfs@vger.kernel.org
Subject: Re: How to make clients NOT block
Date: Sun, 17 Feb 2013 15:49:38 -0500 [thread overview]
Message-ID: <20130217204938.GF11441@fieldses.org> (raw)
In-Reply-To: <680509590.JPpPf8D3KZ@saturn>
On Sat, Feb 16, 2013 at 12:30:07PM +0100, 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.
That's expected.
> Even
> after the NFS server was up again, most clients were stuck to the point they
> had to be rebooted.
But that sounds like a bug, on either client or server.
> What mount options should we use so clients don't block
> completely when the NFS server is gone?
As Boaz says, you can mount with "soft"--but there are good reasons it
isn't the default. (Worst case it can cause data corruption if your
applications aren't extremely careful.)
--b.
> 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
prev parent reply other threads:[~2013-02-17 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 11:30 How to make clients NOT block Michael Monnerie
2013-02-17 14:35 ` Boaz Harrosh
2013-02-17 20:49 ` J. Bruce Fields [this message]
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=20130217204938.GF11441@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lists.michael.monnerie@is.it-management.at \
/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