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.
> 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.
It's why we have Ethernet checksums, IP checksums, TCP/UDP checksums, etc. Defense in depth.
* https://en.wikipedia.org/wiki/IPv4_header_checksum
Skipped in IPv6.
FS-level checksum saves you from the situation when the underlying storage thinks everything is okay but it is not:
> This means there was a data error on the drive. But it’s worse than a typical data error — this is an error that was not detected by the hardware.
* http://changelog.complete.org/archives/9769-silent-data-corr...
* https://research.cs.wisc.edu/wind/Publications/zfs-corruptio...
* https://news.ycombinator.com/item?id=13851349 (via)
It's not an either-or situation, but rather both-and hardware- and FS-level checks.