From: Pavel Machek <pavel@ucw.cz>
To: George Spelvin <linux@horizon.com>
Cc: linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: raid is dangerous but that's secret (was Re: [patch] ext2/3:
Date: Mon, 31 Aug 2009 13:04:48 +0200 [thread overview]
Message-ID: <20090831105645.GD1353@ucw.cz> (raw)
In-Reply-To: <20090831005426.13607.qmail@science.horizon.com>
Hi!
> Actually, there is something the file system can do to make journaling
> safe on degraded RAIDs: make the (checksummed) journal blocks equal to
> the RAID stripe size. Or, equivalently, pad out to the RAID stripe
> size each commit.
>
> This sometimes leads to awkward block sizes, but while writing
> to any *one* stripe on a degraded RAID-5 endangers the others, you
> can write to *all* of them with the usual semantics.
Well, that would work... but you'd also have to journal data, with the
same block size. Not exactly fast, but at least safe...
> That's one thing I really like about ZFS: its policy of "don't trust
> the disks." If nothing else, simply telling you "your disks f*ed up,
> and I caught them doing it", instead of the usual mysterious corruption
> detectec three months later, is tremendoudly useful information.
The more I learn about storage, the more I like idea of zfs. Given the
subtle issues between filesystem and raid layer, integrating them just
makes sense.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-08-31 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 0:54 raid is dangerous but that's secret (was Re: [patch] ext2/3: George Spelvin
2009-08-31 11:04 ` Pavel Machek [this message]
2009-08-31 15:45 ` david
2009-09-01 0:56 ` George Spelvin
2009-09-01 8:36 ` NeilBrown
2009-09-01 8:46 ` Pavel Machek
2009-09-01 11:18 ` George Spelvin
2009-09-01 12:35 ` NeilBrown
2009-09-01 15:25 ` david
2009-09-01 21:12 ` NeilBrown
2009-09-01 16:18 ` Andreas Dilger
2009-09-02 1:10 ` George Spelvin
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=20090831105645.GD1353@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.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).