From: Ric Wheeler <rwheeler@redhat.com>
To: Chris Green <cgreen@valvesoftware.com>
Cc: Neil Brown <neilb@suse.de>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
Mike Snitzer <snitzer@redhat.com>,
Tom Coughlan <coughlan@redhat.com>
Subject: Re: [PATCH] barrier support for other md/raid levels
Date: Fri, 18 Sep 2009 14:28:24 -0400 [thread overview]
Message-ID: <4AB3D148.3060607@redhat.com> (raw)
In-Reply-To: <4D87015385157D4285D56CA6101072FF26C2CCB1@exchange07.valvesoftware.com>
On 09/18/2009 02:19 PM, Chris Green wrote:
> It seems like what you'd need to robustly test barriers is some sort of barrier-supporting loopback device, which
> acted correctly with barriers, but had worst-case behavior without them (buffering things for random arbitrarily long periods of time,
> performing all operations in random order, etc).
>
>
>
I think that it is pretty easy to get corruption (defined as fsck
issues) if we have non-working barriers and do power fail testing. It is
a bit tricky to automate that though but we are working on it,
ric
next prev parent reply other threads:[~2009-09-18 18:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 6:21 [PATCH] barrier support for other md/raid levels Neil Brown
2009-09-18 11:44 ` Ric Wheeler
2009-09-18 18:19 ` Chris Green
2009-09-18 18:28 ` Ric Wheeler [this message]
2009-09-18 18:38 ` Greg Freemyer
2009-09-18 18:43 ` Ric Wheeler
2009-09-18 20:18 ` Majed B.
2009-09-20 21:48 ` Clinton Lee Taylor
2009-09-20 22:57 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2009-09-19 8:58 Michael Guntsche
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=4AB3D148.3060607@redhat.com \
--to=rwheeler@redhat.com \
--cc=cgreen@valvesoftware.com \
--cc=coughlan@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).