Re: Read errors on raid5 ignored, array still clean .. then disaster !!

From
Goswin von Brederlow <hidden>
Date
2010-01-27 09:01:18
Luca Berra [off-list ref] writes:
On Tue, Jan 26, 2010 at 11:28:03PM +0100, Giovanni Tessore wrote:
quoted
Is this some kind of bug?
No
quoted
Is there any way to configure raid in order to have devices marked
faulty on read errors (at least when they clearly become too many)?
I don't think so
quoted
This could (and for me did) bring to big disasters!
Don't agree with you, you had all the info from syslog
You should have run smart tests on the disks and proactively replace a
failing disk.
quoted
In a post of some months ago of a person who had a similar problem,
I read as reply that ignoring the read errors is the wanted
behaviour of md ... but I can't believe this!!
it does _not_ ignore read errors in case of read errors mdadm rewrites
the erroring sector, and only if
this fails it will kick the member out of the array.
with modern drives it is possible to have some failed sector, which the
drive firmware will reallocate on write (all modern drives have a range
of sectors reserved for this very purpose)
mdadm does not do any bookkeeping on reallocated_sector_count per drive
the drive does. the data can be accessed with smartctl
drives showing excessive reallocated_sector_count should be replaced.

Consider the following scenario:
raid5 (sda,b,c,d)
sda has a read error, mdadm kicks it immediately from the array
a few minutes/hours later sdc fails completely
lost data and no time to react, that is far worse than having 50 days of
warnings and ignoring them.
Plus you should have run the raid check as a cron job. In Debian that is
done per default on every first sunday of a month at 3am. The check
reads every stripe from all disks and checks that the parity
matches. That would have caused all read errors of sda to be repaired
or, when the drive runs out of sectors to remap to, kicked the drive.

MfG
        Goswin
Thread (1 message) 1 message, 1 author, last reply 2010-01-27
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help