From: Eric Sandeen <sandeen@redhat.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: "Krzysztof Kosiński" <tweenk.pl@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Massive corruption on RAID0
Date: Tue, 30 Jun 2009 11:46:18 -0500 [thread overview]
Message-ID: <4A4A415A.1070207@redhat.com> (raw)
In-Reply-To: <87f94c370906300942p7c5f576cgbb8c065625cf1716@mail.gmail.com>
Greg Freemyer wrote:
> 2009/6/30 Eric Sandeen <sandeen@redhat.com>:
>> Krzysztof Kosiński wrote:
> <snip>
>>>>> By the way, is there some way to have RAID0-like functionality with
>>> write barriers?
>> Mirrors can pass barriers, IIRC, but not stripes (IIRC...) - I don't
>> know if any work is being done to address this.
>>
> I'm pretty sure mdraid is not attempting to address it.
>
> The issue is that barriers with a single drive can simply be sent to
> the drive for it to do the heavy lifting.
>
> With raid-0, it is much more difficult.
>
> ie. you send a barrier to 2 different drives. One drive takes 30
> milliseconds to flush the pre-barrier queue to disk and then continues
> working on the post barrier data . The other drive takes 500
> milliseconds to do the same. The end result is out of sync barriers.
> Not at all what the filesystem expects.
>
> The only reliable solution is to disable write caching on the drives.
> Of course you don't need barriers then.
Agreed this is the best solution at least for now. But, the dm folks
are apparently working on some sort of barrier solution for stripes, I
think. I don't know the details, perhaps I should.... :)
-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-06-30 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 0:38 Massive corruption on RAID0 Krzysztof Kosiński
2009-06-29 3:30 ` Eric Sandeen
2009-06-29 15:12 ` Krzysztof Kosiński
2009-06-30 15:33 ` Eric Sandeen
[not found] ` <87f94c370906300942p7c5f576cgbb8c065625cf1716@mail.gmail.com>
2009-06-30 16:46 ` Eric Sandeen [this message]
2009-06-30 18:28 ` Mike Snitzer
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=4A4A415A.1070207@redhat.com \
--to=sandeen@redhat.com \
--cc=greg.freemyer@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tweenk.pl@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.