Bryan Mesich <bryan.mesich@xxxxxxxx> wrote: > The most popular mismatch_cnt values are 128 and 256. The worst I=20 > found was 21504 and 7168. I find it interesting that all are=20 > divisible by 128. They should not appear on RAID5. What kinds of filesystems reside on the RAID1s? If it's ext[23] (well, most likely on SANs it's not :)), then these mismatches are very likely located in inode blocks. I've noticed this quite often on RAID1s up to 2.6.26, especially on filesystems with heavy inode fluctuation (remove, create files). Starting with .26 (i guess, maybe later) I didn't see them anymore. Maybe yours on newer kernels are just brownfields? Correct them and see if they appear again? > So, is there anyway to get an output on which blocks do not match? I'd > like to see how they are different, if at all. just cmp -l the components, as you did before md brought up the sync_action check target :) regards Mario -- The question of whether a computer can think is no more interesting than the question of whether a submarine can swim. -- E. W. Dijkstra -- 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
