Equal hash, binary mismatch

[DavorJ]

WARNING: HASH EQUAL, BINARY MISMATCH

No idea how those warnings are possible. Maybe because the hash is computed, then file is changed and backed up, but the hash isn't recomputed. Should be looked into.

Hash computing should be done in the backup. Or some verification mechanism should be implemented so one can check whether the original hash and copied hash match.

This could also have been due to bad clusters, although I don't see any problems with the files itself (mostly .jpg). Also, on one file the difference with the original file was 1890 bytes (all zero's in the backed up version) which doesn't really suggest bad clusters.