Brad Campbell <brad@xxxxxxxxxxx> wrote:
I do occasionally remove/re-add a drive to each array, which causes a full resync of the array and should show up any parity inconsistency by a faulty fsck or md5sum. It has not as yet.
No - it should not show it.
If a bit has flipped on a parity stripe and thus the parity is inconsistent. When I pop out a disk and put it back in, the array is going to be written from parity data that is not quite right. (The problem I believe you were talking about where you have two identical disks and one is inconsistent, which one do you read from? is similar). And thus the reconstructed array is going to have different contents to the array before I failed the disk.
Therefore it should show the error. No?
Brad - 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
