Duplicity fails with "Invalid data - SHA1 hash mismatch for file", does not retry download.
Bug #1360734 reported by
Eric O'Connor
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
New
|
Undecided
|
Unassigned |
Bug Description
There appears to have been a corruption issue in my file download, about halfway through an 80GB restore.
Invalid data - SHA1 hash mismatch for file:
duplicity-
Calculated hash: ee843c75152a61f
Manifest hash: 5971136422f4646
When I checked the file hash on Amazon, it was exactly 5971136422f4646
I would expect duplicity to retry the download when the hash doesn't match.
Duplicity version is: duplicity 0.6.24
Python: 2.7.8
Debian jessie/sid
To post a comment you must log in.
Today it failed on vol442:
Invalid data - SHA1 hash mismatch for file: full.20140720T0 50902Z. vol442. difftar. gpg 88b3b10a528fa98 e2abf15d09 29f35e57aa9a900 5755d16f39
duplicity-
Calculated hash: 9bbdf149dc63077
Manifest hash: 08c31918f9b1133
ec:lair → s3cmd get s3://7e628b/ backup/ duplicity- full.20140720T0 50902Z. vol442. difftar. gpg ./ backup/ duplicity- full.20140720T0 50902Z. vol442. difftar. gpg -> ./duplicity- full.20140720T0 50902Z. vol442. difftar. gpg [1 of 1] duplicity- full.20140720T0 50902Z. vol442. difftar. gpg (string indices must be integers, not str) backup/ duplicity- full.20140720T0 50902Z. vol442. difftar. gpg -> ./duplicity- full.20140720T0 50902Z. vol442. difftar. gpg [1 of 1] full.20140720T0 50902Z. vol442. difftar. gpg 29f35e57aa9a900 5755d16f39 duplicity- full.20140720T0 50902Z. vol442. difftar. gpg
s3://7e628b/
66172 of 67175826 0% in 51s 1290.94 B/s failed
WARNING: Retrying failed request: /backup/
WARNING: Waiting 3 sec...
s3://7e628b/
67175826 of 67175826 100% in 48s 1347.18 kB/s done
ec:lair → sha1sum duplicity-
08c31918f9b1133
Is there a better way than deleting the restore folder and restarting?