On Wed, Apr 23, 2014 at 12:07 AM, NeilBrown <neilb@xxxxxxx> wrote: > On Fri, 11 Apr 2014 17:41:12 +0530 "Manibalan P" <pmanibalan@xxxxxxxxxxxxxx> > wrote: > >> Hi Neil, >> >> Also, I found the data corruption issue on RHEL 6.5. >> >> For your kind attention, I up-ported the md code [raid5.c + raid5.h] >> from FC11 kernel to CentOS 6.4, and there is no mis-compare with the >> up-ported code. > > This narrows it down to between 2.6.29 and 2.6.32 - is that correct? > > So it is probably the change to RAID6 to support async parity calculations. > > Looking at the code always makes my head spin. > > Dan : have you any ideas? > > It seems that writing to a double-degraded RAID6 while it is recovering to > a space can trigger data corruption. > > 2.6.29 works > 2.6.32 doesn't > 3.8.0 still doesn't. > > I suspect async parity calculations. I'll take a look. I've had cleanups of that code on my backlog for "a while now (TM)". -- 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
