I can imagine how one might be missing if it was the last one being sent and it never made it before a forced shutdown. But we handle that case.
The other possible issue is concurrency, but that's not likely. I can see how one volume might go missing, but not 5. ...Ken On Fri, Jul 8, 2011 at 10:49 PM, Michael Terry <michael.te...@canonical.com>wrote: > Ken, when Jorgen talks about GNOME bookmarks, he's talking about using > Deja Dup and selecting a backup from a dropdown populated with GNOME > bookmarks. > > I've been thinking about this bug, and I'm confused. It seems > relatively common, but I can't figure out how duplicity would leave gaps > in the backup. The reporter here had vol15 missing. The reporter from > dup bug 804484 had vol1 through vol5 missing! > > When resuming, duplicity will use what's actually on the backend to > determine what volume to resume at. So I can't see how it would make a > gap that way. These reporters don't seem to be using concurrency or > anything. > > Ken, have you had any ideas here? > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/498933 > > Title: > Crash when restoring data KeyError > > Status in Déjà Dup Backup Tool: > Invalid > Status in Duplicity - Bandwidth Efficient Encrypted Backup: > In Progress > Status in “deja-dup” package in Ubuntu: > Invalid > > Bug description: > Binary package hint: deja-dup > > 1) Ubuntu 9.10 > 2) Deja Dup 10.2-0ubuntu1.1 > 3) I expected my backup to be restored > 4) Deja Dup crashed instead. > > I just tried to restore the backup I made, and it crashes repeatedly > when trying to restore. > > I have it setup to backup my home directory, and tried restoring to > both the original location as well as a completely different folder. > Both lead to the same error message. > > > Traceback (most recent call last): > File "/usr/bin/duplicity", line 825, in <module> > with_tempdir(main) > File "/usr/bin/duplicity", line 818, in with_tempdir > fn() > File "/usr/bin/duplicity", line 775, in main > restore(col_stats) > File "/usr/bin/duplicity", line 436, in restore > restore_get_patched_rop_iter(col_stats)): > File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 521, > in Write_ROPaths > ITR(ropath.index, ropath) > File "/usr/lib/python2.6/dist-packages/duplicity/lazy.py", line 336, in > __call__ > last_branch.fast_process, args) > File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 38, in > check_common_error > return function(*args) > File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 574, > in fast_process > ropath.copy(self.base_path.new_index(index)) > File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 412, in > copy > other.writefileobj(self.open("rb")) > File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 574, in > writefileobj > buf = fin.read(_copy_blocksize) > File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 199, > in read > if not self.addtobuffer(): > File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 224, > in addtobuffer > self.tarinfo_list[0] = self.tar_iter.next() > File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 331, > in next > self.set_tarfile() > File "/usr/lib/python2.6/dist-packages/duplicity/patchdir.py", line 320, > in set_tarfile > self.current_fp = self.fileobj_iter.next() > File "/usr/bin/duplicity", line 472, in get_fileobj_iter > backup_set.volume_name_dict[vol_num], > KeyError: 15 > > ProblemType: Bug > Architecture: i386 > Date: Sun Dec 20 19:59:06 2009 > DistroRelease: Ubuntu 9.10 > ExecutablePath: /usr/bin/deja-dup > InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) > Package: deja-dup 10.2-0ubuntu1.1 > ProcEnviron: > LANG=en_US.UTF-8 > SHELL=/bin/bash > ProcVersionSignature: Ubuntu 2.6.31-16.53-generic > SourcePackage: deja-dup > Uname: Linux 2.6.31-16-generic i686 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/498933 Title: Crash when restoring data KeyError To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/498933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
