Yeah, but as opposed to data corruption, your data will throw an error when you try to read it.
No, the data will be repaired transparently and you won't notice a thing. Errors will be logged, of course, but you'll know that the data is intact.
My preference is the Dynamo / Hadoop / layered approach in which the application is aware of multiple underlying storage devices, and is written in a way that's defensible to underlying device failure.
And ZFS should be the underlying file system upon which these applications are built. If you don't have protection against silent data corruption at the lowest level then you aren't going to have any idea when it happens.
No, the data will be repaired transparently and you won't notice a thing. Errors will be logged, of course, but you'll know that the data is intact.
My preference is the Dynamo / Hadoop / layered approach in which the application is aware of multiple underlying storage devices, and is written in a way that's defensible to underlying device failure.
And ZFS should be the underlying file system upon which these applications are built. If you don't have protection against silent data corruption at the lowest level then you aren't going to have any idea when it happens.