2 ms·
Flash level checksums are an integral part of wear-leveling and flash block allocation strategy. So they are also used for block migration/retirement controls.
by bayindirh 7y ago
Flash 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.
- bayindirh 7y agoMost of the big storage vendors are making it work with Erasure or Hamming Codes. They compensate damaged or missing disks in the arrays transparently and send you a small e-mail about the details of the disk you need to change. RAID-5 and RAID-6 is the most primitive and probably most deployed version of this checksum based compensation and recovery methods. Erasure/Hamming is used for bigger arrays where RAID-5/6 cannot build the disks in a reasonable amount time while they are under I/O load.
- monocasa 7y agoPretty much every NAND flash device out there uses full ECC rather than just a checksum. The whole industry relies on it for yield reasons.
- bayindirh 7y ago> ...flash level checksums on a vertically integrated stack make checksumming again at the FS layer moot... This is simply not true. First, flash is not always the place data ends at. Flash is prevalent in more points in the storage chain. Predominantly on RAID controllers' caches in last 3-5 years and hybrid drives used in laptops. So, flash-level checksumming can guarantee that the data is retrieved in the form it's written and allows neat tricks like wear-leveling and such. On the other hand data can get corrupted in other places. e.g. Data can get corrupted in RAM, bit-rot in hard drives, RAID controllers can add a thick layer of complexity which you cannot manage or the filesystem can just make mistakes due to bugs (I've seen it all). So flash-level checksum can protect the data on the flash, but cannot guarantee that the data is correct in the first place. So if you checksummed the data and wrote it differently, FS or RAID level checksumming will catch it. This will prevent domino effects which the corrupted data can create. Data management gets complicated fast when you need more than a few disk's aggregate capacity with high performance and reliability and, FS level checksumming is a powerful tool to ensure that. > ...assuming you have proper control and reporting on both sides of the block device abstraction boundary. Again this will only guarantee that the device reads the data it has written, but it won't guarantee that it had received the correct data in the first place. > Apple's about the only one who can pull this off with their vertically integrated stack. While Apple can do a lot of exotic stuff with the hardware, it won't be wise to create a custom flash controller and protocol to fuse FS and flash level checksums. It'll increase the software and integration cost, limit their options in hardware scene, slow down product development and plainly limit them in the long run. I had an Intel 4 channel RAID card which corrupted the array when it wakes up from the wrong side of the bed and, it spent hours to verify and rebuild the array from the block level checksums it created on the disks during array creation. I've never lost data, but decided that it didn't worth the effort to keep the array alive and well. So, I eventually ditched it. However its activity LEDs on the board was kinda nice.
- monocasa 7y ago> While Apple can do a lot of exotic stuff with the hardware, it won't be wise to create a custom flash controller and protocol to fuse FS and flash level checksums. It'll increase the software and integration cost, limit their options in hardware scene, slow down product development and plainly limit them in the long run. I mean, tell that to them, because that's what they've done. The T2 chip's feature set is very married to APFS. AFAIK, Linux still doesn't have working drivers for it despite it sort of looking like an NVMe drive.