Re: ATA Defect management

From: bill davidsen
Date: Tue Oct 21 2003 - 15:56:13 EST


In article <200310171037.h9HAbOrv000559@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
John Bradford <john@xxxxxxxxxxxx> wrote:
| [Note to Eric, who is CC'ed, can you comment on how Maxtor drives
| handle these issues?]
|
| Quote from "Norman Diamond" <ndiamond@xxxxxxxxxxxxx>:
| > Friends in the disk drive section at Toshiba said this:
| >
| > When a drive tries to read a block, if it detects errors, it retries up to
| > 255 times. If a retry succeeds then the block gets reallocated. IF 255
| > RETRIES FAIL THEN THE BLOCK DOES NOT GET REALLOCATED.
|
| OK, this is interesting, at least we have some specific information.
|
| > This was so unbelievable to that I had to confirm this with them in
| > different words. In case of a temporary error, the drive provides the
| > recovered data as the result of the read operation and the drive writes the
| > data to a reallocated sector. In case of a permanent error, the block is
| > assumed bad, and of course the data are lost. Since the data are assumed
| > lost, the drive keeps the defective LBA sector number associated with the
| > same defective physical block and it does not reallocate the defective
| > block.

Not so. Assuming the admin is restoring to the same bad drive (the
twit!), since the drive does do relocate on write, the recovery will
work, the data will be whole, and life will be good.

I'm not sure why one would do a by-sector backup, but I guess for some
filesystems or raw database info it might be useful.
--
bill davidsen <davidsen@xxxxxxx>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/