From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ric Wheeler Subject: Re: [PATCH] barrier support for other md/raid levels Date: Fri, 18 Sep 2009 14:28:24 -0400 Message-ID: <4AB3D148.3060607@redhat.com> References: <19123.9980.940255.937839@notabene.brown> <4AB372BA.6020101@redhat.com> <4D87015385157D4285D56CA6101072FF26C2CCB1@exchange07.valvesoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D87015385157D4285D56CA6101072FF26C2CCB1@exchange07.valvesoftware.com> Sender: linux-raid-owner@vger.kernel.org To: Chris Green Cc: Neil Brown , "linux-raid@vger.kernel.org" , Mike Snitzer , Tom Coughlan List-Id: linux-raid.ids 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