Deja Dup fails during restore

Bug #996745 reported by memilanuk
30
This bug affects 7 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I had Ubuntu 11.10 working okay, more or less, a few quirks/bugs in Unity / Dash were annoying the heck out of me. So I decided to do a complete wipe and reinstall of 12.04. On this particular machine I have it dual-booting with Vista, and for linux I have 20GB for /, ~50GB for /home, and ~215GB under /home/share where I store things like backups, iso images, and VirtualBox VMs. The plan was to wipe & reformat / and /home, keep /windows and /home/share, and reinstall, followed by restoring stuff in my home directory from backups stored on /home/share/backups.

Initially things went well. Unity is a bit 'heavier' than I want to run on this particular machine, so I decided to reinstall again, this time with Xubuntu 12.04. I did another backup via Deja Dup, burned a new install disc, and rebooted.

Everything seemed to go okay, but when I was restoring from backups, Deja Dup bombed out with what looks like a python error. Since I had been simultaneously updating and installing new software (a lot of which was python related) I thought maybe something had gotten a little corrupted in the process. So I reinstalled again, applied all the updates, then tried reinstalling. Same errors (as near as I can tell). So I reinstalled *again*... this time I tried restoring *before* downloading and applying all the updates... still no joy. I tried restoring from the previous backup - which did work before, thinking it might be a problem with the backup files themselves - still nothing.

Here is the errors I'm getting (pardon any typos, I'm having to manually type it from one machine to another to post this...)

Traceback (most recent call last):
File "/usr/bin/duplicity", line 1403, in <module>
  with_tempdir(main)
File "/usr/bin/duplicity", line 1396, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1330, in main
  restore(col_stats)
File "/usr/bin/duplicity", line 623, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/
patchdir.py", line 495, in integrate_patch_iters
  final_ropath = patch_seq2ropath(normalize_ps(patch_seq)
)
File "/usr/lib/python2.7/dist-packages/duplicity/
patchdir.py", line 475, in patch_seq2ropath
  misc.copyfileobj(current_file, tempfp)
File "/usr/lib/python2.7/dist-packages/duplicity/misc.py",
line 166, in copyfileobj
  buf = infp.read(blocksize)
File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py",
line 80, inread
  self, add_to_outbuf_once()
File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py",
line 94, in _add_to_outbuf_once
  raise librsyncError(str(e))
librsyncError: librsync error 103 while in patch cycle

if I'm reading that right, librsync is coughing up an error, which is then raising all the way up thru the application code and causing Deja Dup to bomb out. So whats causing librsync to fail?

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: deja-dup 22.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Tue May 8 13:16:41 2012
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
memilanuk (memilanuk) wrote :
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
Lunarts (lunartsbr-gmail) wrote :

I also am having problems, with the restore failing at the patch part also. My backup files are very important, if I cannot recover my backups I'm doomed(too). Also using Xubuntu(12.10).

Revision history for this message
Lunarts (lunartsbr-gmail) wrote :
Revision history for this message
Noel Arzola (noel.arzola) wrote :

has anyone tested that patch? the errors listed in that bug linked are different than the errors we are experiencing. Not sure how to apply it to test it myself

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.