Hi list!
Is it possible for tarsnap to show exactly what changed in which files, when creating a new archive, preferably with --dry-run?
Or maybe it is possible for "-t -v -f <archive>" to show some sort of file checksum so that I can see what differences there are between two archives?
I backup an external drive using tarsnap. Unfortunately, this drive's filesystem (HFS+) became corrupted in a way that meant while I still had read-only access I couldn't get write access. I was able to copy its contents onto my laptop, reformat the drive with a new HFS+ filesystem, and copy everything back onto the drive. Hooray!
However, I'm a bit paranoid that during all this copying I may have had some bits flip and corrupted my data somehow. I've no real reason to believe this is the case, but I hoped that tarsnap would actually be able to tell me.
I made a new archive with --dry-run and I'm told that a new archive would use 8.8MB of data from a total data size of ~120GB. That sounds like it could be 8.8MB of metadata has changed during the copying, or 8.8MB of data has been corrupted. Can tarsnap tell me exactly what's changed, if anything?
Thanks!
Ed