public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: John Stoffel <john@stoffel.org>
Cc: Robin Lee Powell <rlpowell@digitalkingdom.org>,
	linux-kernel@vger.kernel.org
Subject: Re: NFS hang + umount -f: better behaviour requested.
Date: Tue, 21 Aug 2007 12:55:44 -0400	[thread overview]
Message-ID: <20070821165544.GA27995@fieldses.org> (raw)
In-Reply-To: <18123.5699.405125.137517@stoffel.org>

On Tue, Aug 21, 2007 at 12:43:47PM -0400, John Stoffel wrote:
> Robin> I've read every man page I could find, and the only nfs option
> Robin> that semes even vaguely helpful is "soft", but everything that
> Robin> mentions "soft" also says to never use it.
> 
> I think the man pages are out of date, or ignoring reality.

No.  The price of using "soft" is the chance of data corruption, since
an application may for example be left thinking that a write has
succeeded when it hasn't.  See

	http://nfs.sourceforge.net/#faq_e4

--b.

  reply	other threads:[~2007-08-21 16:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 22:54 NFS hang + umount -f: better behaviour requested Robin Lee Powell
2007-08-20 23:27 ` Neil Brown
2007-08-20 23:34   ` Robin Lee Powell
2007-08-21  1:51     ` Salah Coronya
2007-08-21 16:43 ` John Stoffel
2007-08-21 16:55   ` J. Bruce Fields [this message]
2007-08-21 17:01   ` Peter Staubach
2007-08-21 17:14     ` Chakri n
2007-08-21 17:14     ` Robin Lee Powell
2007-08-21 17:18       ` Peter Staubach
2007-08-21 18:50     ` John Stoffel
2007-08-21 19:04       ` Peter Staubach
2007-08-21 19:25       ` J. Bruce Fields
2007-08-24 15:09         ` Ric Wheeler
2007-08-24 15:37           ` Peter Staubach
2007-08-24 15:53           ` J. Bruce Fields
2007-08-21 23:04       ` Valdis.Kletnieks
2007-08-22 10:03         ` Theodore Tso
2007-08-22 15:26         ` John Stoffel
2007-08-31  8:06       ` Ian Kent
2007-08-31 15:10         ` Valdis.Kletnieks
2007-08-31 15:30           ` Ian Kent

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=20070821165544.GA27995@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=john@stoffel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlpowell@digitalkingdom.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