All, I'm seeing a non-zero mismatch_cnt (in fact, it's 1704) on my RAID-6 array consisting of 8 devices on kernel 2.6.38. After replacing some hardware, I decided to trigger a MD repair by issuing: echo repair > /sys/devices/virtual/block/md5/md/sync_action Directly after issuing this command, the mismatch_cnt is reset to 0 and MD starts checking the array. However, the mismatch_cnt increases during this check - resulting in exactly the same count as seen before. Shouldn't 'repair' yield a zero mismatch_cnt? I think I have seen 'repair' work on other RAID-6 arrays? Furthermore, theoretically it should be possible to indicate which device in the RAID-6 array contains the inconsistent data, or am I mistaking? If so, that would certainly be a nice feature to see implemented, as it would help diagnosing problems. Please let me know your thoughts, as I'm quite keen to get my mismatch_cnt back to 0 in order to see whether the new hardware works properly! Thanks, Bas -- 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
