Guy wrote:
Bad sectors are detected on write. There are 5 wires going to each of the
Bad sectors can be detected both on write and on read. Unfortunately,
most time there will be *read* error -- it is pretty possible for the
drive to perform a read-check after write, and the data may be ok at
that time, but not when you will want to read it a month later...
read/write heads on my disk drives. I think each head can read after write
in 1 pass. My specs say it re-maps on write failure and read failure. Both
are optional. But, I don't know if this is normal or not. My disks are
Seagate ST118202LC, 10,000 RPM, 18 Gig SCSI.
I think all modern drives support bad block remapping on both read and write.
But think about it: if there's a read error, it means the drive CAN NOT read
the "right" data for some reason (for some definition of "right" anyway) --
ie, the drive "knows" there's some problem with the data and it can't
completely reconstruct what has been written to the block before. In this
case, while remapping the block in question help to avoid further error in
this block, it does NOT help to restore the data which the drive can't read.
And sure it is not an option in this case to report that read was successeful
and to pass, say, zero-filled block to the controller... ;)
/mjt
-
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
