On Thu, 17 May 2007, Greg Oster wrote:
> The only reason a parity check should fail is if one of the 
> components has errors

Oh, did somebody fix the issues with shutdown doing stuff in the wrong
order, leaving raidframe parity dirty in some cases even without any
hardware failures?  (ISTR that using swap on raid was one of the easier
ways of triggering this bug.)

--apb (Alan Barrett)