On 01/22/2010 11:22 AM, Jon Hardcastle wrote:
<SNIP>
Note that if your md device is not in a read-only mode that the
member states may be changing underneath you as you run the above
command. Therefore, you should either stop the device then run the
commands, or at least have the device in a read-only mode first.
-BR
I have just tried this - i umounted all LV and then deactivated the
VG. I set to read-only but now any attempt to echo check>
sync_action results in
Sorry for the misunderstanding, I was suggesting putting the array in
read only mode only for the purposes of doing the 'mdadm --examine' to
detect if member devices were out of sync with each other.
But, it turns out that the mismatches you're seeing are not a result of
the member devices being out of sync with each other but rather member
devices throwing errors. Sounds like other people see this same
behavior and it's not necessarily tied to any disk sector read errors.
If there are also no I/O errors in the kernel log during your 'check'
operation, you'll need either more verbose md logging during the check
or a look at the code to see what other kinds of errors bump the
mismatch counter.
-BR
--
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
