>I recently created a de novo backup of some personal data on an external HFS+ >drive (photos, movies, music, etc). I was very unpleasantly surprised to find >several files had been silently corrupted. (In the case of a movie file, for >example, the file would play but could not be copied. In another case, a music >file would not copy, yet it had identical md5sum and sha1 checksums when >compared to an uncorrupted redundant backup I had. I’m still puzzled by this, >but it suggests the resource fork might be the source of the corruption, and, >more worrisome still, that conventional checksums aren’t detecting some >silently corrupted data, so I am not even sure if zfs self-healing would be >the answer.)
Might be some sort of copyright-protecting feature of the files, to prevent piracy. Why should file corruption prevent copying per se, anyway? JPK
