Deja-dup backup failed with SHA1 mismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
deja-dup (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Invalid data - SHA1 hash mismatch for file:
duplicity-
Calculated hash: 519a55451ec0543
Manifest hash: 614f06ba1bfe919
happens regularly on different machines
Restore from there impossible even older backups are not accessible
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: deja-dup 32.0-0ubuntu1.1
ProcVersionSign
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 21 12:26:56 2015
InstallationDate: Installed on 2013-05-17 (644 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)
Strange!
I found a workaround which irritates me.
I moved all previous backups to a different location.
Next backup starts with a full backup which -> WORKS
I do a differential backup immediately afterwards -> WORKS
I move the old backups into place again and gain access to my old backup and the new differentials work.
Unfortunately deja-dup does not make a full backup on demand. One has to trick it into doing it (or wait for the mechanism to kick in)
Now to the irritation:
Why does the differential work now and did not work before? There is no indication as to the backup forward-chaining encryption (It uses gpg - well actually duplicity does). So how can the SHA1 checksums differ?
For this bug: It could be closed as far as I am concerned but the issue requires further investigation.