3 ms·
The oversimplified answer is that ZFS’ in-memory structures are not designed to minimize bitflip risk, as some file systems are. Content is hashed when written
by adastra22 11mo ago
The oversimplified answer is that ZFS’ in-memory structures are not designed to minimize bitflip risk, as some file systems are. Content is hashed when written to memory cache, but it can be a long time before it then gets to disk. Very little validation is done at that point to protect against writing bad data.
- abrookewood 11mo agoWhat file systems offer in-memory protection?
- magicalhippo 11mo ago> it can be a long time before it then gets to disk Well by default the timeout is 5 seconds[1], so not that long. [1]: https://openzfs.github.io/openzfs-docs/Performance%20and%20Tuning/Module%20Parameters.html#zfs-txg-timeout https://openzfs.github.io/openzfs-docs/Performance%20and%20T...
- adastra22 11mo agoThat is a long time from this perspective.
- magicalhippo 11mo agoThere's also a max size, so if you have heavy write traffic it'll flush do disk much earlier. The timeout is just for low-write scenarios.