AssertionError: 4 while making an incremental backup

Bug #1271927 reported by leder
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
New
Undecided
Unassigned

Bug Description

duplicity 0.6.21-0ubuntu4.1
python3.3 3.3.2-7ubuntu3 and
python2.7 2.7.5-8ubuntu3 installed!
log not found?!

With Ubuntu 13.10 duplicity used to work with Ubuntu One backup and an initial backup.

Now, when weekly backup occurs, the incremential backup fails with unknown error: Thanks in advance!

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1414, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1407, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1341, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 635, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 466, in patch_seq2ropath
    assert len( patch_seq ) == 1, len( patch_seq )
AssertionError: 4

Revision history for this message
edso (ed.so) wrote :

can you reproduce the error? doing a full and an incremental afterwards?

..ede/duply.net

Revision history for this message
leder (gerrit-leder) wrote :

Here is what I did:
- delete existing backup folder in Ubuntu One for old full and incrementals
- start a "deja-dup --backup"
- Expected result: full backup in Ubuntu One and success message
- Actual result: full backup in Ubuntu One folder exists, but I get an error message about a non existent "metadata":
»/home/leder/.cache/deja-dup/metadata« konnte nicht wiederhergestellt werden: Datei wurde in der Sicherung nicht gefunden.

As for configuration the folder /home/leder/.cache is excluded from the backup!

Bye
Gerrit

Revision history for this message
leder (gerrit-leder) wrote :

This is what I did next:
- touch test
- change a previously backed up file (update)
- deja-dup --backup

- expected result: incremental backup is created, no errors
- actual result: incremental backup was created, I had some minor owner permission issues shown:
/home/leder/.cache/dconf
/home/leder/.gvfs
/home/leder/.viminfo
were all owned by root and I did next:
- sudo su
- chown leder.leder .cache/dconf .gvfs .viminfo
- deja-dup --backup

- expected result: incremental backup is created, no errors
- actual result: incremental backup was created, no errors (as expected)

This concludes to the error in the description being not reproducible BUT:
mentioned in the previous post and this post the folders deja-dup/metadata and dconf are read in the backup process, though the enclosing folder .cache is excluded by deja-dup configuration from the backup!

I hope that the recovery would be OK, but I do not know how to test that without erasing my home folder.

Thanks all
Gerrit

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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