* bad block checking and repair
@ 2008-10-23 12:31 Keld Jørn Simonsen
0 siblings, 0 replies; only message in thread
From: Keld Jørn Simonsen @ 2008-10-23 12:31 UTC (permalink / raw)
To: linux-raid
Is there a case for better bad block handling in linux raid?
Disk errors are reported to be more and more frequent in today's
systems. Storage capacity grows and with that the likelihood of disk
errors.
I am not sure of the ststus of bad block handling in linux raid.
Can somebody enlighten me?
I think there are a number of techniques that could be employed.
1. checking an array - full scan, and occasionally examining the SMART
error log, eg. every gigabyte, then rewrite the data with reported
errors. Then check the SMART error log again and for the errors still
reported move it to a bad block area and remap the affected data.
2. When irrecoverable errors have occurred, then check which drive was
affected, and remap the bad data on the bad disk, using the data of the
sound drive (for raids with redundant data).
Is this viable techniques? I think something like this could be built
into the raid check functionality.
best regards
keld
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-10-23 12:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-10-23 12:31 bad block checking and repair Keld Jørn Simonsen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).