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 -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
