From: David Woodhouse <dwmw2@infradead.org>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: raild[56] again
Date: Tue, 04 May 2010 16:09:09 +0100 [thread overview]
Message-ID: <1272985749.31892.5621.camel@macbook.infradead.org> (raw)
In-Reply-To: <14154949.31.1272916930325.JavaMail.root@zimbra>
On Mon, 2010-05-03 at 22:02 +0200, Roy Sigurd Karlsbakk wrote:
> Is raid[56] coming to btrfs? There was some talk about it a year back
> or so, but I haven't seen anything yet....
Um, there was some talk about it about four days ago. You even
participated in that thread!
As it stands, it has the traditional 'write hole' problem -- when you
overwrite _part_ of a stripe, you have to update the parity block(s) too
and you have a short period of time where the parity doesn't match the
actual data. If you get a crash followed by a disk failure during that
period of time, you get data loss.
The solution is always to write a full stripe (across all the disks in
the set). Chris said he'd sort that out in the upper layers of btrfs,
about which I know little. We've been waiting a while for that.
I poked him recently and we realised that I hadn't actually made my part
_cope_ with being given a full stripe at a time, which was a bit of an
oversight. I had done it once as a test, but had never actually
committed and pushed that support. The patch I posted last week attempts
to fix that. There are one or two details I wanted some feedback on but
in the absence of that, I think I'll just tidy it up and push it using
the existing approach.
--
dwmw2
next prev parent reply other threads:[~2010-05-04 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 20:02 raild[56] again Roy Sigurd Karlsbakk
2010-05-03 20:27 ` Tomasz Torcz
2010-05-04 15:09 ` David Woodhouse [this message]
2010-05-04 15:11 ` Chris Mason
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=1272985749.31892.5621.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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).