Why would you not be happy? resyncs in general are bad since they indicate your data is possibly out-of-sync and the resync itself consumes an enormous amount of resources
This is a feature of new-ish md driver code that more aggressively marks the array as "clean" after writes The end result is that the array will most likely be "clean" in all circumstances even a crash, and you simply won't need to resync That's a good thing! -Mike Kasper Dupont wrote: > I have a FC4 installation (upgraded from FC3) using kernel > version 2.6.15-1.1831_FC4. I see some symptoms in the software > raid, which I'm not quite happy about. > > After an unclean shutdown caused by a crash or power failure, > it does not resync the md devices. I have tried comparing the > contents of the two mirrors for each of the md devices. And I > found that on the swap device, there were differences. > > Isn't this a bug in the software raid? Shouldn't it always > resync after reboot, if there could possibly be any difference > between the contents on the two disks? > > I know that as long as only swap is affected, it is not going > to cause data loss. But how can I be sure it is not going to > happen on file systems as well? > > Should I report this as a bug in Fedora Core or did I miss > something? > - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
