On Sat, 6 Dec 2008, Michal Soltys wrote:
Justin Piszcz wrote:
when tler is on, why does linux not attempt to remap the sector?
See my earlier posts on this question from last week. It would need a
metadata section on each HDD to keep track of the bad sectors before it
writes to the drives, a 3ware card will do this for you-- however,
typically, (having run md/linux) for a number of years is not
super-necessary if you run checks on your disks once a week *AND* you have
good drives that don't have problems.
From what I know, md does attempt to repair read errors (but not other ones
though) with rewrite, and only if it fails, it will kick the drive out of the
array. In case of 1.x superblocks, the count of repaired (+ ones not causing
drive to be kicked off) sectors will be preserved across reboots as well
(check Documentation/md.txt). Peeking over the code seems to confirm it as
well.
It appears so:
[ 1215.654712] raid5:md3: read error not correctable (sector 213000256 on sde1).
[ 1215.654765] raid5: Disk failure on sde1, disabling device.
[ 1215.654766] raid5: Operation continuing on 8 devices.
[ 1215.655412] raid5:md3: read error not correctable (sector 213000264 on sde1).
[ 1215.655473] raid5:md3: read error not correctable (sector 213000272 on sde1).
[ 1215.655533] raid5:md3: read error not correctable (sector 213000280 on sde1).
[ 1215.655592] raid5:md3: read error not correctable (sector 213000288 on sde1).
[ 1215.655644] raid5:md3: read error not correctable (sector 213000296 on sde1).
[ 1215.655694] raid5:md3: read error not correctable (sector 213000304 on sde1).
[ 1215.655746] raid5:md3: read error not correctable (sector 213000312 on sde1).
[ 1215.655800] raid5:md3: read error not correctable (sector 213000320 on sde1).
[ 1215.655852] raid5:md3: read error not correctable (sector 213000328 on sde1).
Justin.
--
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
