Deja-dup backup failed with SHA1 mismatch

Bug #1424164 reported by Wolf Rogner
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Invalid data - SHA1 hash mismatch for file:
 duplicity-inc.20150220T070946Z.to.20150221T110727Z.vol1.difftar.gpg
 Calculated hash: 519a55451ec0543774c06023ed4b6a36e1bf8db8
 Manifest hash: 614f06ba1bfe919a0a7dd8aba8a3ce945b95f4e2

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
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: nvidia wl
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)

Revision history for this message
Wolf Rogner (war-rsb) wrote :
Revision history for this message
Wolf Rogner (war-rsb) wrote :

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.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deja-dup (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in deja-dup (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.