Restore fails with "Invalid data - SHA1 hash mismatch"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Incomplete
|
High
|
Kenneth Loafman | ||
Déjà Dup |
Invalid
|
Critical
|
Unassigned | ||
duplicity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When restoring a backup, one might see an error like:
Invalid data - SHA1 hash mismatch:
Calculated hash: 0b2bc4c2fb98b36
Manifest hash: 11cd330357618de
This can happen when a volume file was not completely written to the backend before duplicity was interrupted (say, shutting down the machine or whatever). When duplicity resumes the backup next run, it will start with the next volume. The half-complete volume file will sit on the backend and cause this error later when restoring.
You can manually recover from this by either restoring from your older backup sets or by restoring individual files that don't happen to be in the corrupted volume.
== To Reproduce ==
See attachment https:/
== Ubuntu SRU Justification ==
This is a serious data loss problem for users, which won't be noticed until they try to restore. With Ubuntu 11.10 including Deja Dup, some users may think to back up their data first then upgrade, and may accidentally create corrupted backups.
Changed in duplicity: | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
Changed in duplicity: | |
milestone: | none → 0.6.07 |
Changed in duplicity: | |
milestone: | 0.6.07 → 0.6.08 |
Changed in duplicity: | |
milestone: | 0.6.08 → 0.6.09 |
Changed in deja-dup: | |
importance: | Undecided → Critical |
status: | In Progress → Confirmed |
Changed in duplicity: | |
milestone: | none → 0.6.14 |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
status: | In Progress → Fix Committed |
Changed in deja-dup: | |
status: | Confirmed → Invalid |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Changed in duplicity (Ubuntu): | |
status: | New → Fix Released |
description: | updated |
Changed in duplicity (Ubuntu Lucid): | |
status: | New → Confirmed |
Changed in duplicity (Ubuntu Maverick): | |
status: | New → Confirmed |
Changed in duplicity (Ubuntu Natty): | |
status: | New → Confirmed |
tags: |
added: verification-done removed: verification-needed |
tags: | added: verification-done-natty |
tags: | removed: verification-done |
Ken, do you know what's going on here? Is this a case of a bad/stale archive-dir?