On Tuesday March 6, rabbit@xxxxxxxxx wrote: > > > > I see. So basically for those of us who want to run swap on raid 1 or > 10, and at the same time want to rely on mismatch_cnt for early problem > detection, the only option is to create a separate md device just for > the swap. Is this about right? Though it is less likely, a regular filesystem could still (I think) genuinely write different data to difference devices in a raid1/10. So relying on mismatch_cnt for early problem detection probably isn't really workable. And I think that if a drive is returning bad data without signalling an error, then you are very much into the 'late' side of problem detection. I see the 'check' and 'repair' functions mostly as valuable for the fact that they read every block and will trigger sleeping bad blocks early. If they every find a discrepancy, then it is either perfectly normal, or something seriously wrong that could have been wrong for a while.... NeilBrown - 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
