On 7/20/2012 7:53 AM, Jaromir Capik wrote: > I admit, that the problem could lie elsewhere ... but that doesn't > change anything on the fact, that the data became corrupted without > me noticing that. The key here I think is "without me noticing that". Drives normally cry out in the night, spitting errors to logs, when they encounter problems. You may not receive an immediate error in your application, especially when the drive is a RAID member and the data can be shipped regardless of the drive error. If you never check your logs, or simply don't see these disk errors, how will you know there's a problem? Likewise, if the checksumming you request is implemented in md/RAID1, and your application never sees a problem when a drive heads South, and you never check your logs and thus don't see the checksum errors... How is this new checksumming any better than the current situation? The drive is still failing and you're still unaware of it. -- Stan -- 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
