In my case it turns out that two of the volumes were truncated somehow. Not sure if this is the sort of filesystem corruption that can occur when a removable volume is disconnected without unmounting it, but that would probably make sense.
Unfortunately the deja-dup GUI has no way to recover from this problem and gives you no options on how to skip the affected files, it just reports the difftar file name which is less than helpful. I had to go decrypt and look through the manifest as noted above to figure out which files needed to be skipped when restoring (in this case, there was only one file, a very large audio recording that was thankfully backed up elsewhere). Nor does duplicity or deja-dup do anything to detect that this problem might exist when adding incremental backups (the truncated volumes were in a full backup from two months ago with several incrementals since). In the appears that I can restore from the command line (the links in a comment above from *thirteen years ago* are obviously no longer valid) using the --exclude option to duplicity. Truly deja-dup is an overly simplified GUI, having some options and robustness is not a luxury when dealing with important data. Amazing that neither of these pieces of software seem to have improved since then. Perhaps backups aren't important to developers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/487720 Title: Restore fails with "Invalid data - SHA1 hash mismatch" To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/487720/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
