Re:What’s New in Apple Filesystems [pdf]
by throw0101a on Thursday June 13, 2019 @09:48AM
(#20174785)
It tells you that your data is corrupted, which gives you options on dealing with the situation.
> If your application can deal with data loss it can deal with bit flips too.
No, it may not. The file may mostly be okay except for a place where a single bit flip causes the value to go from positive to negative:
* https://en.wikipedia.org/wiki/Signed_number_representations
Hardware not-handling bit flips is a documented phenomenon per my citations above. It does cause issues further up the stack. FS-level checksumming gives people the option to at least detect these errors, and depending on the situation, also perhaps fix them.
People already have a much better option by doing checksumming if necessary on the application level, much closer to the source of data actually with even less possibilities to miss corruption.
Re:What’s New in Apple Filesystems [pdf]
by throw0101a on Thursday June 13, 2019 @10:19AM
(#20175104)
Yes, doing it at the application level would be better. But doesn't preclude it doing it at other layers as well.
It's why we have Ethernet checksums, IP checksums, TCP/UDP checksums, etc. Defense in depth.
We don't have IP checksums, and only have TCP and UDP checksums because it's optional on Ethernet, and TCP/UDP doesn't always run over Ethernet anyway.
Re:What’s New in Apple Filesystems [pdf]
by throw0101a on Friday June 14, 2019 @08:12AM
(#20182307)
Headers:
* https://en.wikipedia.org/wiki/IPv4_header_checksum
Skipped in IPv6.
It doesn't save you from anything, it just turns bit flips into full blocks of data loss and introduces overhead. If your application can deal with data loss it can deal with bit flips too. Filesystem-level checksumming is still useless.