On 25/02/2010 08:05, Giovanni Tessore wrote: [...]
I see this is the 4th time in a month that poeple reports problem on raid5 due to the read errors during reconstruction; it looks like the 'corrected read errors' policy is quite a real concern.
If you mean md's policy of reconstructing from the other discs and rewriting when there's a read error from one disc of an array, rather than immediately kicking the disc that had a read error, I think you're wrong - I think md is saving lots of users from hitting problems, by keeping their arrays up and running, and giving their discs a chance to remap bad sectors, instead of forcing the user to do full-disc reconstructions more often which will make them more likely to hit read errors during recovery.
I do think we urgently need the hot reconstruction/recovery feature, so failing drives can be recovered to fresh drives with two sources of data, i.e. both the failing drive and the remaining drives in the array, giving us two chances of recovering every sector.
Cheers, John. -- 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
