Neil Brown wrote:
The 'check' process reads all copies and compares them with one
another, If there is a difference it is reported. If you use
'repair' instead of 'check', the difference is arbitrarily corrected.
If a read error is detected during the 'check', md/raid1 will attempt
to write the data from the good drive to the bad drive, then read it
back. If this works, the drive is assumed to be fixed. If not, the
bad drive is failed out of the array.
One thing to note here is that 'repair' was broken for RAID1 until
recently - see
http://marc.theaimsgroup.com/?l=linux-raid&m=116951242005315&w=2
As this patch was submitted just prior to the release of 2.6.20, this
may be the first "fixed" kernel, but I have not checked.
Regards,
Richard
-
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
