[Bug 662442] Re: restore fails with "librsync error 103 while in patch cycle"
*** This bug is a duplicate of bug 1252484 ***
https://bugs.launchpad.net/bugs/1252484
Hi,
I am not sure if this is related, but I am certainly hoping someone can
assist
I'm struggling to restore backups from an older installation of Ubuntu
to a new installation on Ubuntu 16.04. I get the following error when
trying to restore:
Failed with an unknown error Followed by:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1532, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1526, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1380, in main
do_backup(action)
File "/usr/bin/duplicity", line 1461, in do_backup
list_current(col_stats)
File "/usr/bin/duplicity", line 698, in list_current
for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 354, in
combine_path_iters
refresh_triple_list(triple_list)
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 341, in
refresh_triple_list
new_triple = get_triple(old_triple[1])
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 327, in
get_triple
path = path_iter_list[iter_index].next()
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 239, in
sigtar2path_iter
for tarinfo in tf:
File "/usr/lib/python2.7/tarfile.py", line 2508, in next
tarinfo = self.tarfile.next()
File "/usr/lib/python2.7/tarfile.py", line 2350, in next
raise ReadError("unexpected end of data")
ReadError: unexpected end of data
The backup completed successfully but I cannot get it to restore.
Thanks in advance!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with "librsync error 103 while in patch cycle"
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
*** This bug is a duplicate of bug 1252484 *** https://bugs.launchpad.net/bugs/1252484 Good news! I've confirmed this is the same underlying issue as bug 1252484 (which I will mark this bug a duplicate of). This is just one of its symptoms. I've attached the file 'test5.sh' which when run like 'sh test5.sh' should reliably reproduce this exception. This bug has been fixed in duplicity trunk (and Ubuntu 13.10+). The fix will be in the upcoming duplicity 0.6.23 release. I've prepared fixes for older Ubuntu releases, but the updates need testers before they can be released to everyone. If you are an Ubuntu user of an older release, please go to bug 1252484 and follow the instructions for testing the update. Thanks! ** Attachment added: test5.sh https://bugs.launchpad.net/duplicity/+bug/662442/+attachment/3925044/+files/test5.sh ** This bug has been marked a duplicate of bug 1252484 Possible data loss when restarting in the middle of a deleted file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I still haven't found the source of this bug. But I have filed a branch [1] that is basically a glorified version of the patch in comment 6. This lets the rest of the restore continue when this error happens, though obviously without the problem file. (It will log an error about that file, so users will notice.) Hopefully that will reduce the severity of this bug, but we should keep this bug open for the original problem. [1] https://code.launchpad.net/~mterry/duplicity/catch-seq-copy- error/+merge/186106 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
A coworker (Steve Magoun) graciously lent me a backup data set of his that reproduces this problem. What appears to have happened on his data set (and presumably others who are experiencing this) is that a file (say, test.txt) gets backed up in the initial full backup at time A. This initial backup seems fine. Later, the file is included in an incremental backup at time B. But for some reason, the patch that duplicity creates is seemingly against a different basis file than the recorded at time A. So when restoring, the patch does not apply to the stored time A version of the file. When restoring from time B, duplicity will complain but not error out. It will create a half-finished test.txt. If you restore from a later time point, duplicity will error out and create no file. Here is the librsync output from my example data. (original basis file is an xml text file 68664 bytes large) You can see at the end, it tries to read from the basis file past its end. So the patch seems to be against a different (larger) basis file than we have. I'm not sure how this could happen yet, but I figured I'd dump these thoughts here. original call to rs_job_iter here python2.7: (rs_scoop_readahead) got 4 bytes from input buffer python2.7: (rs_scoop_advance) advance over 4 bytes from input buffer python2.7: (rs_patch_s_header) got patch magic 0x72730236 python2.7: (rs_scoop_readahead) got 1 bytes from input buffer python2.7: (rs_scoop_advance) advance over 1 bytes from input buffer python2.7: (rs_patch_s_cmdbyte) got command byte 0x42 (LITERAL), len_1=2 python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_patch_s_run) running command 0x42, kind 1001 python2.7: (rs_patch_s_literal) LITERAL(len=512) python2.7: (rs_tube_catchup_copy) copied 512 bytes from input buffer, 0 remain to be copied python2.7: (rs_scoop_readahead) got 1 bytes from input buffer python2.7: (rs_scoop_advance) advance over 1 bytes from input buffer python2.7: (rs_patch_s_cmdbyte) got command byte 0x4a (COPY), len_1=2 python2.7: (rs_scoop_readahead) got 4 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_patch_s_run) running command 0x4a, kind 1003 python2.7: (rs_patch_s_copy) COPY(where=512, len=24064) python2.7: (rs_patch_s_copying) copy 24064 bytes from basis at offset 512 python2.7: (rs_patch_s_copying) copy callback returned OK python2.7: (rs_patch_s_copying) got 24064 bytes back from basis callback python2.7: (rs_scoop_readahead) got 1 bytes from input buffer python2.7: (rs_scoop_advance) advance over 1 bytes from input buffer python2.7: (rs_patch_s_cmdbyte) got command byte 0x42 (LITERAL), len_1=2 python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_patch_s_run) running command 0x42, kind 1001 python2.7: (rs_patch_s_literal) LITERAL(len=5084) python2.7: (rs_tube_catchup_copy) copied 5084 bytes from input buffer, 0 remain to be copied python2.7: (rs_scoop_readahead) got 1 bytes from input buffer python2.7: (rs_scoop_advance) advance over 1 bytes from input buffer python2.7: (rs_patch_s_cmdbyte) got command byte 0x4a (COPY), len_1=2 python2.7: (rs_scoop_readahead) got 4 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_patch_s_run) running command 0x4a, kind 1003 python2.7: (rs_patch_s_copy) COPY(where=29696, len=512) python2.7: (rs_patch_s_copying) copy 512 bytes from basis at offset 29696 python2.7: (rs_patch_s_copying) copy callback returned OK python2.7: (rs_patch_s_copying) got 512 bytes back from basis callback python2.7: (rs_scoop_readahead) got 1 bytes from input buffer python2.7: (rs_scoop_advance) advance over 1 bytes from input buffer python2.7: (rs_patch_s_cmdbyte) got command byte 0x42 (LITERAL), len_1=2 python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_readahead) got 2 bytes from input buffer python2.7: (rs_scoop_advance) advance over 2 bytes from input buffer python2.7: (rs_patch_s_run) running command 0x42, kind 1001 python2.7: (rs_patch_s_literal) LITERAL(len=2048) python2.7: (rs_tube_catchup_copy) copied 2048 bytes from input buffer, 0 remain to be copied python2.7: (rs_scoop_readahead) got 1 bytes from input buffer python2.7: (rs_scoop_advance) advance over 1 bytes from input
Re: [Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
The link to the source http://atoaudiovisual.com/x/duplicity_joiner.py seems to be broken On 6 September 2013 02:18, David Huss da...@huss.at wrote: For those who still want (or have to) to restore their backups by hand, I found a solution for me. The unpack-part is easy, the stich/join-part is not. So I wrote an application for that. More details here: http://blog.atoaudiovisual.com/2013/09/restore-broken-deja-dup-backup-hand/ -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- Martin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
For those who still want (or have to) to restore their backups by hand, I found a solution for me. The unpack-part is easy, the stich/join-part is not. So I wrote an application for that. More details here: http://blog.atoaudiovisual.com/2013/09/restore-broken-deja-dup-backup-hand/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
thx for the patch.. rescued my stuff successfully... now going for a more robust backup tool :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I have the same problem. I used the patch Christopher Foo provided (many thanks for that!) - but unfortunately the outcome is the same as what gluca reports. Would be very grateful for help -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I have the same problem. The restoration of the home gives the error librsync error 103 while in patch cycle. After applying the pacth, I can restore individual home folder, but not the entire home, it shows the error AssertionError: first.difftype! = Diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I added a try/catch around the faulty lines (like the one in the patch) and get it going through the restore. just missing sevral files (logs, gnome config DB, etc.). I just got a bad feeling about it since my backup is my 'last ressort' when something goes wrong (here a HD crash). I expect it to be bullet- proof. I hope duplicity will fix it since it is still a sooo great software for backup. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Had this happen to me a year ago -- my mistake was failing to test the restore immediately after the initial backup. I'm using grsync at this point, a not-great but at least adequate substitute. On 07/24/2013 12:53 AM, Frederic Dreier wrote: I added a try/catch around the faulty lines (like the one in the patch) and get it going through the restore. just missing sevral files (logs, gnome config DB, etc.). I just got a bad feeling about it since my backup is my 'last ressort' when something goes wrong (here a HD crash). I expect it to be bullet- proof. I hope duplicity will fix it since it is still a sooo great software for backup. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I tried the given patch but it still crash.
Error 'librsync error 103 while in patch cycle' processing
home/john/.eclipse/org.eclipse.platform_3.8_155965261/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info
Traceback (most recent call last):
File ./bin/duplicity, line 1403, in module
with_tempdir(main)
File ./bin/duplicity, line 1396, in with_tempdir
fn()
File ./bin/duplicity, line 1330, in main
restore(col_stats)
File ./bin/duplicity, line 624, in restore
restore_get_patched_rop_iter(col_stats)):
File /tmp/duplicity/duplicity/patchdir.py, line 532, in Write_ROPaths
for ropath in rop_iter:
File /tmp/duplicity/duplicity/patchdir.py, line 505, in
integrate_patch_iters
final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
File /tmp/duplicity/duplicity/patchdir.py, line 463, in patch_seq2ropath
assert first.difftype != diff, patch_seq
AssertionError: [(('home', 'john', '.eclipse',
'org.eclipse.platform_3.8_155965261', 'configuration', 'org.eclipse.osgi',
'bundles', '80', 'data', '-741665970', 'artifacts.xml') reg)]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with librsync error 103 while in patch cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I have the same problem. I really need to restore some files from my backup and it is ending with this error librsyncError: librsync error 103 while in patch cycle There is no file in my backup without .gpg manuall recovery as suggested is causing the same error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Constantin, to fix the error you see in your comment #26, delete the file duplicity-full.20130307T152041Z.vol1001.difftar (note how there is no .gpg after it). To see instructions for manually recovering, see https://live.gnome.org/DejaDup/Help/Restore/WorstCase (especially near the bottom). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Is there a completely manual way to restore? Removing the encryption shouldn't be to hard but it's an incremental backup and I worry about stitching the files together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I managed to compile but it still doesn't work. This really unfortunate
since this is my only backup of all documents (well partially that's in
the cloud), photos and music. I updated it before formatting and now I'm
pretty much fucked.
Below's the output.
tantin@Ubook:~/Desktop/duplicity$ sudo ./bin/duplicity restore --gio --force
'file:///media/tantin/8c9dba0f-0fcb-4d18-a0a8-4d22af8356e8/gpg'
'/home/tantin/backup'
Local and Remote metadata are synchronized, no sync needed.
Traceback (most recent call last):
File ./bin/duplicity, line 1403, in module
with_tempdir(main)
File ./bin/duplicity, line 1396, in with_tempdir
fn()
File ./bin/duplicity, line 1276, in main
globals.archive_dir).set_values()
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 698, in
set_values
self.get_backup_chains(partials + backend_filename_list)
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 821, in
get_backup_chains
map(add_to_sets, filename_list)
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 811, in
add_to_sets
if set.add_filename(filename):
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 97, in
add_filename
(self.volume_name_dict, filename)
AssertionError: ({1: 'duplicity-full.20130307T152041Z.vol1.difftar', 2050:
'duplicity-full.20130307T152041Z.vol2050.difftar.gpg', 2056:
'duplicity-full.20130307T152041Z.vol2056.difftar.gpg', 2059:
'duplicity-full.20130307T152041Z.vol2059.difftar.gpg', 2061:
'duplicity-full.20130307T152041Z.vol2061.difftar.gpg', 14:
'duplicity-full.20130307T152041Z.vol14.difftar.gpg', 16:
'duplicity-full.20130307T152041Z.vol16.difftar.gpg', 2068:
'duplicity-full.20130307T152041Z.vol2068.difftar.gpg', 2075:
'duplicity-full.20130307T152041Z.vol2075.difftar.gpg', 28:
'duplicity-full.20130307T152041Z.vol28.difftar.gpg', 30:
'duplicity-full.20130307T152041Z.vol30.difftar.gpg', 2086:
'duplicity-full.20130307T152041Z.vol2086.difftar.gpg', 41:
'duplicity-full.20130307T152041Z.vol41.difftar.gpg', 2092:
'duplicity-full.20130307T152041Z.vol2092.difftar.gpg', 46:
'duplicity-full.20130307T152041Z.vol46.difftar.gpg', 47:
'duplicity-full.20130307T152041Z.vol47.difftar.gpg', 51:
'duplicity-full.20130307T152041Z.vol51
.difftar.gpg', 52: 'duplicity-full.20130307T152041Z.vol52.difftar.gpg', 2105:
'duplicity-full.20130307T152041Z.vol2105.difftar.gpg', 62:
'duplicity-full.20130307T152041Z.vol62.difftar.gpg', 2111:
'duplicity-full.20130307T152041Z.vol2111.difftar.gpg', 65:
'duplicity-full.20130307T152041Z.vol65.difftar.gpg', 2:
'duplicity-full.20130307T152041Z.vol2.difftar', 67:
'duplicity-full.20130307T152041Z.vol67.difftar.gpg', 74:
'duplicity-full.20130307T152041Z.vol74.difftar.gpg', 77:
'duplicity-full.20130307T152041Z.vol77.difftar.gpg', 78:
'duplicity-full.20130307T152041Z.vol78.difftar.gpg', 79:
'duplicity-full.20130307T152041Z.vol79.difftar.gpg', 2062:
'duplicity-full.20130307T152041Z.vol2062.difftar.gpg', 86:
'duplicity-full.20130307T152041Z.vol86.difftar.gpg', 87:
'duplicity-full.20130307T152041Z.vol87.difftar.gpg', 2137:
'duplicity-full.20130307T152041Z.vol2137.difftar.gpg', 2140:
'duplicity-full.20130307T152041Z.vol2140.difftar.gpg', 93:
'duplicity-full.20130307T152041Z.vol93.difftar.gpg',
2142: 'duplicity-full.20130307T152041Z.vol2142.difftar.gpg', 2064:
'duplicity-full.20130307T152041Z.vol2064.difftar.gpg', 2146:
'duplicity-full.20130307T152041Z.vol2146.difftar.gpg', 99:
'duplicity-full.20130307T152041Z.vol99.difftar.gpg', 100:
'duplicity-full.20130307T152041Z.vol100.difftar.gpg', 109:
'duplicity-full.20130307T152041Z.vol109.difftar.gpg', 110:
'duplicity-full.20130307T152041Z.vol110.difftar.gpg', 2159:
'duplicity-full.20130307T152041Z.vol2159.difftar.gpg', 112:
'duplicity-full.20130307T152041Z.vol112.difftar.gpg', 113:
'duplicity-full.20130307T152041Z.vol113.difftar.gpg', 2164:
'duplicity-full.20130307T152041Z.vol2164.difftar.gpg', 121:
'duplicity-full.20130307T152041Z.vol121.difftar.gpg', 2170:
'duplicity-full.20130307T152041Z.vol2170.difftar.gpg', 123:
'duplicity-full.20130307T152041Z.vol123.difftar.gpg', 125:
'duplicity-full.20130307T152041Z.vol125.difftar.gpg', 127:
'duplicity-full.20130307T152041Z.vol127.difftar.gpg', 2391:
'duplicity-full.20130307T152041Z.vol
2391.difftar.gpg', 133: 'duplicity-full.20130307T152041Z.vol133.difftar.gpg',
139: 'duplicity-full.20130307T152041Z.vol139.difftar.gpg', 141:
'duplicity-full.20130307T152041Z.vol141.difftar.gpg', 142:
'duplicity-full.20130307T152041Z.vol142.difftar.gpg', 147:
'duplicity-full.20130307T152041Z.vol147.difftar.gpg', 151:
'duplicity-full.20130307T152041Z.vol151.difftar.gpg', 2202:
'duplicity-full.20130307T152041Z.vol2202.difftar.gpg', 155:
'duplicity-full.20130307T152041Z.vol155.difftar.gpg', 156:
'duplicity-full.20130307T152041Z.vol156.difftar.gpg', 159:
'duplicity-full.20130307T152041Z.vol159.difftar.gpg', 161:
'duplicity-full.20130307T152041Z.vol161.difftar.gpg', 162:
Re: [Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I tried and never could make it work. Lost a lot of work. On 06/01/2013 09:41 AM, Constantin Gindele wrote: Is there a completely manual way to restore? Removing the encryption shouldn't be to hard but it's an incremental backup and I worry about stitching the files together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Michael, all, I'm trying to restore one of my backups that DejaDup saved to my NAS. Until now I have been unsuccessfull in doing so. My machine is Ubuntu 12.10 and I haven't tried the patching thing yet. here is the CLI output but I'm happy to dig further upon advice. $ duplicity --file-to-restore home/seb ftp://backup@10.1.1.6/backup/deja-dup/snoopy2 /media/seb/ext4_backup/recover/20121213 NcFTP version is 3.2.5 Synchronising remote metadata to local cache... GnuPG passphrase: Copying duplicity-full-signatures.20121213T154732Z.sigtar.gpg to local cache. Copying duplicity-full.20121213T154732Z.manifest.gpg to local cache. Copying duplicity-inc.20121213T154732Z.to.20121220T074758Z.manifest.gpg to local cache. Copying duplicity-inc.20121220T074758Z.to.20121227T000634Z.manifest.gpg to local cache. Copying duplicity-inc.20121227T000634Z.to.20130103T070657Z.manifest.gpg to local cache. Copying duplicity-inc.20130103T070657Z.to.20130110T064523Z.manifest.gpg to local cache. Copying duplicity-inc.20130110T064523Z.to.20130126T065714Z.manifest.gpg to local cache. Copying duplicity-inc.20130126T065714Z.to.20130131T105745Z.manifest.gpg to local cache. Copying duplicity-inc.20130131T105745Z.to.20130208T113225Z.manifest.gpg to local cache. Copying duplicity-new-signatures.20121213T154732Z.to.20121220T074758Z.sigtar.gpg to local cache. Copying duplicity-new-signatures.20121220T074758Z.to.20121227T000634Z.sigtar.gpg to local cache. Copying duplicity-new-signatures.20121227T000634Z.to.20130103T070657Z.sigtar.gpg to local cache. Copying duplicity-new-signatures.20130103T070657Z.to.20130110T064523Z.sigtar.gpg to local cache. Copying duplicity-new-signatures.20130110T064523Z.to.20130126T065714Z.sigtar.gpg to local cache. Copying duplicity-new-signatures.20130126T065714Z.to.20130131T105745Z.sigtar.gpg to local cache. Copying duplicity-new-signatures.20130131T105745Z.to.20130208T113225Z.sigtar.gpg to local cache. Warning, found incomplete backup sets, probably left from aborted session Last full backup date: Thu Dec 13 16:47:32 2012 python: ERROR: (rs_file_copy_cb) unexpected eof on fd5 python: ERROR: (rs_job_complete) patch job failed: unexpected end of input Traceback (most recent call last): File /usr/bin/duplicity, line 1412, in module with_tempdir(main) File /usr/bin/duplicity, line 1405, in with_tempdir fn() File /usr/bin/duplicity, line 1339, in main restore(col_stats) File /usr/bin/duplicity, line 630, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 522, in Write_ROPaths for ropath in rop_iter: 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, in read 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 I'd be willing to discuss the sharing of my backup... its only 92 GB :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Just to give an update:
I used the patch Chris indicated / attached to manually patch
patchdir.py. I wasn't able to compile Duplicity, but when I tried
restoring my backup again it ran past the error - but I'm experiencing a
different error now (below)!
In terms of Adriano's question asking in which directory to run the
patch: From the errors above, I found the patchdir.py file in
/usr/lib/python2.7/dist-packages/duplicity.
The error I now get is a different error, I think unrelated to this
specific bug report, but here is the new error anyway:
Traceback (most recent call last):
File /usr/bin/duplicity, line 1411, in module
with_tempdir(main)
File /usr/bin/duplicity, line 1404, in with_tempdir
fn()
File /usr/bin/duplicity, line 1338, in main
restore(col_stats)
File /usr/bin/duplicity, line 632, in restore
restore_get_patched_rop_iter(col_stats)):
File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 532, in
Write_ROPaths
for ropath in rop_iter:
File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 505, in
integrate_patch_iters
final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 463, in
patch_seq2ropath
assert first.difftype != diff, patch_seq
AssertionError: [(('home', 'stuart', '.config', 'chromium', 'Default', 'History
Index 2013-04') reg), (('home', 'stuart', '.config', 'chromium', 'Default',
'History Index 2013-04') reg), (('home', 'stuart', '.config', 'chromium',
'Default', 'History Index 2013-04') reg), (('home', 'stuart', '.config',
'chromium', 'Default', 'History Index 2013-04') reg), (('home', 'stuart',
'.config', 'chromium', 'Default', 'History Index 2013-04') reg), (('home',
'stuart', '.config', 'chromium', 'Default', 'History Index 2013-04') reg),
(('home', 'stuart', '.config', 'chromium', 'Default', 'History Index 2013-04')
reg), (('home', 'stuart', '.config', 'chromium', 'Default', 'History Index
2013-04') reg), (('home', 'stuart', '.config', 'chromium', 'Default', 'History
Index 2013-04') reg), (('home', 'stuart', '.config', 'chromium', 'Default',
'History Index 2013-04') reg)]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with librsync error 103 while in patch cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
If anyone has a copy of a backup with this bug that they'd be willing to share, please let me know. We haven't been able to reproduce this error yet. :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I also experience this bug. The backups I'm trying to restore are from my old Ubuntu 13.04 system - but actually one on which I installed the xubuntu-desktop package on top of - and trying to restore to a new computer with plain Ubuntu 13.04. I saw a request for logs from before applying the patch, and afterwards. Below is my before log, whereafter I'll apply the patch mentioned above. Log: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, 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 479, 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, in read 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
In which directory should i run patch -p0 ../duplicity_hax_662442_for_rev884.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Thank you for the detailed instructions! I managed to build however I
had to install python-dev and librsync-dev as well two get around the
errors
Python.h: No such file or directory
and
librsync.h: No such file or directory
The commands are
sudo apt-get install python-dev
and
sudo apt-get install librsync-dev
However I now get this error
Traceback (most recent call last):
File ./bin/duplicity, line 1403, in module
with_tempdir(main)
File ./bin/duplicity, line 1396, in with_tempdir
fn()
File ./bin/duplicity, line 1276, in main
globals.archive_dir).set_values()
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 698, in
set_values
self.get_backup_chains(partials + backend_filename_list)
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 821, in
get_backup_chains
map(add_to_sets, filename_list)
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 811, in
add_to_sets
if set.add_filename(filename):
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 93, in
add_filename
self.set_manifest(filename)
File /home/tantin/Desktop/duplicity/duplicity/collections.py, line 124, in
set_manifest
remote_filename)
AssertionError:
('duplicity-inc.20130307T152041Z.to.20130404T084858Z.manifest.gpg',
'duplicity-inc.20130307T152041Z.to.20130404T084858Z.manifest')
So the quest to restore continues...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/662442
Title:
restore fails with librsync error 103 while in patch cycle
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I second the request on a quick how-to apply the patch for the less knowledgeable people (like my self) encountering the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Sorry, I didn't see comment #17. This comment addresses #17 and #18 and any future readers. First note, a disclaimer: I am *not* a developer nor maintainer of duplicity. Ok, first open up a terminal. It should be in the Accessories menu. Now type the following and hit enter. Do so for any commands listed from now on. sudo apt-get install build-essential bzr Enter your password if prompted and hit yes to install the software. Once it's installed, let's switch the current directory to somewhere obvious like the Desktop folder. Use command: cd Desktop Now download the software. Use command: bzr branch lp:duplicity There should be a duplicty folder on your Desktop now. Now grab the my hax file patch and put it on the Desktop. Ok, now switch to the duplicity folder. Run command: cd duplicity Before we apply to patch, we need to switch to older code. Run command: bzr revert -r884 Now run the command to patch. The double dot indicates it's saved one level outside the current folder, the Desktop folder. Run command: patch -p0 ../duplicity_hax_662442_for_rev884.diff It should say patching file duplicity/patchdir.py. Now switch to the folder duplicity/ (aka ~/Desktop/duplicity/duplicity). Run command: cd duplicity Compile something. Run command: python compilec.py Now switch back to the parent dir. Run command: cd .. Now duplicity should be ready to run. You can run ./bin/duplicity. This command will show the version. Run command: ./bin/duplicity -V It will return $version which isn't set, but the main thing is that it successfully runs. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I have run into the same problem trying to restore my backups. The error I get is - Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, 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 479, 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, in read 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 I have tried using a more up to date version, tried using an earlier version, but I get the same error every time. Is there a way I can get the backups back ? the entire backup folder is about 165gb and most of it I'd rather no lose if possible. I noticed there's a patch mentioned, but in all honesty I'm not sure how to apply it, so I'm willing to give that a go, if someone has an idiot proof guide on how to apply the patch. And if there's anything else I can try I'd be happy to have a go, really don't want to lose the data. I'm running linux mint 14 (have previously run mint and used deja dup with no issues) current deja dup version - 26.0~bzr1443.43~quantal1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Here's a hint at what might be going wrong. While working on the Python 3 port of duplicity, I started getting this error. It turned out to be because I accidentally closed the patch basis file too soon. Maybe some code path here is closing a file we need for rsync patching too early. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
I'm having the same issue on gentoo ** Changed in: duplicity Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
full file can be found here if patch gets rejected: http://www.binrand.com/post/4368177-path-index-dan-duplicity.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: duplicity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
** Also affects: duplicity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662442] Re: restore fails with librsync error 103 while in patch cycle
The attachment Emergency hax patch that skips the unpatchable file of this bug report has been identified as being a patch. The ubuntu- reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report. [This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662442 Title: restore fails with librsync error 103 while in patch cycle To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/662442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
