Re: Blockbusting news, results end

[Norman Diamond]

Eric Mudama wrote:

> If a drive wants to reallocate a block, but due to some temporary
> condition is unable to (vibration, excessive temperature, etc), odds are
> there's no way for that drive to "remember" that it needs to reassign that
> block, so if you reboot the drive or reset it or whatever, you're back at
> square 1.

Bingo.  This is why reallocation at the time of a failed read is also
necessary.  Yes the data are lost, yes the failure needs to be both logged
(once) and displayed to the user (once), yes if an application reads it
again before writing then it will be garbage or zeroes, but get the LBA
sector number moved to a place that is less likely to be unreliable.

Meanwhile software must still make up for defective firmware.

-
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/