On 13 Jun 2006, Gordon Henderson said: > On Tue, 13 Jun 2006, Adam Talbot wrote: >> Can any one give me more info on this error? Pulled from >> /var/log/messages. >> "raid6: read error corrected!!" > > Not seen that one!!! The message is pretty easy to figure out and the code (in drivers/md/raid6main.c) is clear enough. The block device driver has reported a read error. In the old days (pre-2.6.15) the drive would have been kicked from the array for that, and the array would have dropped to degraded state; but nowadays the system tries to rewrite the stripe that should have been there (computed from the corresponding stripes on the other disks in the array), and only fails if that doesn't work. Generally hard disks activate sector sparing and stop reporting read errors for bad blocks only when the block is *written* to (it has to do that, annoying though the read errors are; since it can't read the data off the bad block, it can't tell what data should go onto the spare sector that replaces it until you write it). So it's disk damage, but unless it happens over and over again you probably don't need to be too conerned anymore. -- `Voting for any American political party is fundamentally incomprehensible.' --- Vadik - 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
