On Thursday August 19, bugzilla@xxxxxxxxxxxxxxxx wrote: > Why does it check the parity and not just write the correct parity? Because on a mostly-in-sync array, checking the parity is faster than correcting the parity. > Does it log the count that were wrong, or anything? no, but one day it will. > > And does your new --update=resync option do the same thing? It just marks an in-sync array as not-in-sync so that a resync is forced. It will do the same check-and-correct process for raid5. 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
