From: Theodore Tso <tytso@mit.edu>
To: Valdis.Kletnieks@vt.edu
Cc: John Stoffel <john@stoffel.org>,
Peter Staubach <staubach@redhat.com>,
Robin Lee Powell <rlpowell@digitalkingdom.org>,
linux-kernel@vger.kernel.org
Subject: Re: NFS hang + umount -f: better behaviour requested.
Date: Wed, 22 Aug 2007 06:03:25 -0400 [thread overview]
Message-ID: <20070822100325.GB25150@thunk.org> (raw)
In-Reply-To: <29735.1187737456@turing-police.cc.vt.edu>
On Tue, Aug 21, 2007 at 07:04:16PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 21 Aug 2007 14:50:42 EDT, John Stoffel said:
>
> > Now maybe those issues are raised when you have a Linux NFS server
> > with Solaris clients. But in my book, reliable NFS servers are key,
> > and if they are reliable, 'soft,intr' works just fine.
>
> And you don't need all that ext3 journal overhead if your disk drives
> are reliable too. Gotcha. :)
Err, no. The ext3 journal overhead buys you not needing to fsck after
an unclean shutdown, and safety against crap getting written to the
inode table on an unclean power hit while the disk drive is writing
and the memory goes insane before the DMA engine and disk drive stop
working from the voltage on the power supply rails. (Hence my advice
that if you use XFS on Linux, make *sure* you have a UPS; on machines
such as the SGI Indy they added bigger capacitors to the PSU and a
real power fail interrupt, but PC-class hardware is
inexpensive/crappy, so it doesn't have such niceties.)
- Ted
next prev parent reply other threads:[~2007-08-22 10:03 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
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 [this message]
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=20070822100325.GB25150@thunk.org \
--to=tytso@mit.edu \
--cc=Valdis.Kletnieks@vt.edu \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlpowell@digitalkingdom.org \
--cc=staubach@redhat.com \
/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