4 ms·
Yeah, but as opposed to data corruption, your data will throw an error when you try to read it. It's just a different failure mode. In production, SSDs will oft
by sargun 13y ago
Yeah, but as opposed to data corruption, your data will throw an error when you try to read it. It's just a different failure mode. In production, SSDs will often accept a write, take a sync/flush (acknowledge they've been written to durable storage), and when reading them back, they will not return the same data that was previously written out to them.
Mirroring is also part of ZFS, but it's not ZFS magic. 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.
- chongli 13y agoYeah, 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.
- sargun 13y agoOnly if you mirror the data. If you only have one copy of the data, it wont magically repair itself.