Mattias Wadenstein wrote:
On Mon, 7 Jan 2008, Thiemo Nagel wrote:
What you call "pathologic" cases when it comes to real-world data are
very common. It is not at all unusual to find sectors filled with
only a constant (usually zero, but not always), in which case your
**512 becomes **1.
Of course it would be easy to check how many of the 512 Bytes are
really different on a case-by-case basis and correct the exponent
accordingly, and only perform the recovery when the corrected
probability of introducing an error is sufficiently low.
What is the alternative to recovery, really? Just erroring out and
letting the admin deal with it, blindly assume that the parity is wrong?
Currently, 'repair' does blind recalculation of parity. The only
benefit of that is (correct me if I'm wrong) to ascertain repeated reads
return identical data.
The last time I checked, there was not even a warning message.
Kind regards,
Thiemo Nagel
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
