6 ms·
There is a lot of discussion online. Most of it can be found by searching for "hfs bitrot" on Google. https://blog.barthe.ph/2014/06/10/hfs-plus-bit-rot/ https
by taspeotis 10y ago
There is a lot of discussion online. Most of it can be found by searching for "hfs bitrot" on Google.
https://blog.barthe.ph/2014/06/10/hfs-plus-bit-rot/ https://blog.barthe.ph/2014/06/10/hfs-plus-bit-rot/
> A concrete example of Bit Rot
> ... HFS+ lost a total of 28 files over the course of 6 years.
- astrange 10y agoA bad filesystem would have corrupt metadata. Plain old corrupt data is the fault of the storage media, which does have its own error correction. Clearly it wasn't good enough, or the path from the HD back to the system can't report I/O errors. BTW he didn't lose any data, since he had backups. If he had a checksummed filesystem, but not backups, he would still have lost data. Checksums, like RAID, aren't backups!
- coldtea 10y agoAnd the conclusion of the author itself --in the end of the post-- was that it was due to bad hardware, not HSF+. To quote: >I understand the corruptions were caused by hardware issues. My complain is that the lack of checksums in HFS+ makes it a silent error when a corrupted file is accessed. This not an issue specific to HFS+. Most filesystems do not include checksums either. Sadly…
- coldtea 10y ago(Downvotes for being accurate? I'm not sure how even the "disagree" downvote applies here, as there's nothing to disagree with).