5 ms·
However the flash memory knows the checksum on the hardware level, and running its own internal checks for data integrity. Flash controllers reserve a certain
by bayindirh 7y ago
However the flash memory knows the checksum on the hardware level, and running its own internal checks for data integrity.
Flash controllers reserve a certain amount of blocks for CRC and check summing, so flash is much more intelligent and knowledgeable than it seems.
- throw0101a 7y ago> * However the flash memory knows the checksum on the hardware level, and running its own internal checks for data integrity.* Assuming that the flash controller has no bugs and doesn't fetch the wrong sector/LBA. The OS asks for LBA X, but instead Y is fetched, and the sum(Y) passes so the data is sent back as "OK". If you don't have checksums at a layer above the hardware, how do you know if the right sector was sent to you? (I've seen reports of ZFS catching errors like this.)
- bayindirh 7y agoYes, that's a possibility. Flash level checksum only guarantees that the written or read LBA is intact. However, I've never seen an enterprise storage system to do a mistake like that. My archaic OCZ Vectors or Mac SSDs also didn't do something similar. The problem you mention is as sinister as bit-rot. It's always nice that the FS is self aware about its integrity, however it may be overkill for consumer class devices and installations. Maybe making the flash controller and the storage itself more reliable should be better in the long run for these type of devices IMHO.
- monocasa 7y agoFlash level checksums also generally cover the flash translation layer (ie. the mapping of physical to logical sectors). It's probably not needed for a vertically integrated stack of APFS on a Apple SSD controller. It'd be nice to have fir external drives though.
- bayindirh 7y agoFlash level checksums are an integral part of wear-leveling and flash block allocation strategy. So they are also used for block migration/retirement controls. In other words, it's not trivial or desirable to remove flash level ECC or other checksums from physical flash management layer. I cannot find the article now, but the flash storage is way less reliable than it seems and it's correcting bit errors silently without reporting most of the time. This article [0] shows some of the things behind the curtain in flash storage configuration and lifetime. I'd edit or add the other article if I can find it. [0]: https://goughlui.com/2015/04/05/teardown-optimization-comsol-8gb-usb-flash-stick-au6989sn-gt-sdtnrcama-008g/ https://goughlui.com/2015/04/05/teardown-optimization-comsol...
- monocasa 7y agoI'm saying that flash level checksums on a vertically integrated stack make checksumming again at the FS layer moot, assuming you have proper control and reporting on both sides of the block device abstraction boundary. Apple's about the only one who can pull this off with their vertically integrated stack.
- zzzcpan 7y agoAnyone can pull this off, because filesystem level checksumming without an additional place to recover data from is useless.
- bayindirh 7y agoExchange the checksumming with hamming codes or with another ECC system with >=2 bit detection/correction capability and you're all set.
- zzzcpan 7y agoNot really set, but even assuming you can make it work this is already way beyond checksumming the lack of which people complain about for some reason.
- throw0101a 7y ago> However, I've never seen an enterprise storage system to do a mistake like that. Unless you're using a checksumming file system (a la ZFS), how would you know? And even if you were using ZFS, it would probably just do a re-read from another part of the mirror/RAID-Z and fix it behind the scenes. That's the issue with people saying "things are fine": how do they actually know since we're not verifying things? Up until fairly recently, we haven't really been looking too closely, simply trusting the lower levels of the stack: * http://www.cs.toronto.edu/~bianca/papers/fast08.pdf http://www.cs.toronto.edu/~bianca/papers/fast08.pdf