4 ms·
What specifically are you replying to? I'm not sure I recognize something in the article this applies to (but that could just be me interpreting what was prese
by kbenson 7y ago
What specifically are you replying to? I'm not sure I recognize something in the article this applies to (but that could just be me interpreting what was presented differently than you).
- the8472 7y ago> One fundamental reason is that ZFS is philosophically and practically opposed to rewriting existing data on disk; once written, it wants everything to be completely immutable ZFS was not philosophically opposed to those ideas. They were just dropped at some point.
- nickik 7y agoThey were dropped because getting them fully correct and implemented was really hard and required a lot of work that nobody really wanted to pay for.
- phs2501 7y agoWhat's funny is now ZFS is used on SSDs, where that kind of rewriting is constantly happening behind the scenes (even if you're not writing it's constantly doing housekeeping for degraded blocks, especially on modern denser flash).