geky

3 ms·

1. 1.▲
   by geky 7y ago

   Honestly most file systems haven't been designed to run on an FTLs (except maybe UBIFS). Most filesystems have been designed to run on magnetic disk drives, where wear is a non-issue and data locality is more important. As the world tr
2. 2.▲
   by geky 7y ago

   There's also some cases where you don't care about the devices that develop errors. Wear-leveling delays wear errors until the end of the device's life. Once these start to develop you will eventually have storage that's
3. 3.▲
   by geky 7y ago

   You could as a sanity check, it would be useful to insure no corrupted data gets passed into your system. Though this wouldn't protect the filesystem completely.
4. 4.▲
   by geky 7y ago

   Error correction provides the same value as a checksum, but better. (the tradeoff is ECC codes are much larger and more expensive to compute) It's also worth noting the CRC is used for power-loss and doesn't actually provide error
5. 5.▲
   by geky 7y ago

   I'm not sure I'm following this snap operation. What is a "log tail" in this context? Does this the snap operation still work if we are copying over entries of the log lazily and we don't have a definite end-of-log?
6. 6.▲
   by geky 7y ago

   Reading through 2.3.5 (Lists and Garbage Collection), it looks like it's describing a tree where the leaf nodes also contain references to the root of the next tree. This wouldn't work as a copy-on-write tree, as the root node is