Neil Brown wrote:
On Monday March 5, eyal@xxxxxxxxxxxxxx wrote:
Neil Brown wrote:
[trim Q re how resync fixes data]
For raid1 we 'fix' and inconsistency by arbitrarily choosing one copy
and writing it over all other copies.
For raid5 we assume the data is correct and update the parity.
Can raid6 identify the bad block (two parity blocks could allow this
if only one block has bad data in a stripe)? If so, does it?
No, it doesn't.
I guess that maybe it could:
Rebuild each block in turn based on the xor parity, and then test
if the Q-syndrome is satisfied.
but I doubt the gain would be worth the pain.
What's the value of "I have a drive which returned bad data" vs. "I have
a whole array and some part of it returned bad data?" What's the cost of
doing that identification, since it need only be done when the data are
inconsistent between the drives and give a parity or Q mismatch? It
seems easy, given that you are going to read all the pertinent sectors
into memory anyway.
If the drive can be identified the data can be rewritten with confidence.
--
bill davidsen <davidsen@xxxxxxx>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
-
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
