Brad Campbell <brad@xxxxxxxxxxx> wrote:
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?
It will not detect it as an error, if that is what you mean.
Now here we have a difference of opinion.
I'm detecting errors using md5sums and fsck.
If the drive checks out clean 1 minute, but has a bit error in a parity stripe and I remove/re-add a drive the array is going to rebuild that disk from the remaning data and parity. Therefore the data on that drive is going to differ compared to what it was previously.
Next time I do an fsck or md5sum I'm going to notice that something has changed. I'd call that an error.
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
