From: Eric Sandeen <sandeen@sandeen.net>
To: Moshe Yudkowsky <moshe@pobox.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-raid@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: RAID needs more to survive a power hit, different /boot layout for example (was Re: draft howto on making raids for surviving a disk crash)
Date: Mon, 04 Feb 2008 10:45:19 -0600 [thread overview]
Message-ID: <47A7411F.2040702@sandeen.net> (raw)
In-Reply-To: <47A72FBC.9090701@pobox.com>
Moshe Yudkowsky wrote:
> So if I understand you correctly, you're stating that current the most
> reliable fs in its default configuration, in terms of protection against
> power-loss scenarios, is XFS?
I wouldn't go that far without some real-world poweroff testing, because
various fs's are probably more or less tolerant of a write-cache
evaporation. I suppose it'd depend on the size of the write cache as well.
-Eric
next prev parent reply other threads:[~2008-02-04 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 19:15 RAID needs more to survive a power hit, different /boot layout for example (was Re: draft howto on making raids for surviving a disk crash) Moshe Yudkowsky
2008-02-03 20:01 ` Robin Hill
2008-02-03 20:46 ` Moshe Yudkowsky
2008-02-03 22:01 ` Robin Hill
2008-02-04 11:06 ` Moshe Yudkowsky
2008-02-04 11:40 ` Robin Hill
2008-02-03 20:28 ` Michael Tokarev
2008-02-03 20:54 ` Moshe Yudkowsky
2008-02-03 21:04 ` Michael Tokarev
2008-02-04 9:27 ` Michael Tokarev
2008-02-04 10:58 ` Moshe Yudkowsky
2008-02-04 13:52 ` Michael Tokarev
2008-02-04 14:09 ` Justin Piszcz
2008-02-04 14:25 ` Eric Sandeen
2008-02-04 14:42 ` Eric Sandeen
2008-02-04 15:31 ` Moshe Yudkowsky
2008-02-04 16:45 ` Eric Sandeen [this message]
2008-02-04 17:22 ` Michael Tokarev
2008-02-05 12:31 ` Linda Walsh
2008-02-04 16:38 ` Michael Tokarev
2008-02-04 19:02 ` Richard Scobie
2008-02-04 22:27 ` Justin Piszcz
2008-02-06 1:12 ` Linda Walsh
2008-02-06 2:12 ` Michael Tokarev
2008-02-06 9:14 ` Luca Berra
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=47A7411F.2040702@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=moshe@pobox.com \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).