On 01/19/2010 05:04 AM, Jon Hardcastle wrote:
I kicked off a check/repair cycle on my machine after i moved the phyiscal ordering of my drives around and I am now on my second check/repair cycle and it has kept finding mismatches. Is it correct that the mismatch value after a repair was needed should equal the value present after a check? What if it doesn't? What does it mean if another check STILL reveals mismatches? I had something similar after i reshaped from raid 5 to 6 i had to run check/repair/check/repair several times before i got my 0.
I think to diagnose this you'll need to show us the results of running 'mdadm -E /dev/[hs]dX#' (i.e. /dev/sda2) for each member device in the md device you're trying to assemble *before* attempting to start the md device. This will report on the state of that specific member device (partition) and will show why a resync/repair would/would not be needed.
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 -- 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
