Duplicity

Restore failure from Ubuntu 12.10

Asked by Jim Pearson

Hi all,

I have attached the Bug ID #1093095 but thought I would also pose a question to see if someone could give me some pointers to see if I could try to recover the data:

DUPLICITY: ERROR 30 librsyncError
DUPLICITY: . Traceback (most recent call last):
DUPLICITY: . File "/usr/bin/duplicity", line 1404, in <module>
DUPLICITY: . with_tempdir(main)
DUPLICITY: . File "/usr/bin/duplicity", line 1397, in with_tempdir
DUPLICITY: . fn()
DUPLICITY: . File "/usr/bin/duplicity", line 1331, in main
DUPLICITY: . restore(col_stats)
DUPLICITY: . File "/usr/bin/duplicity", line 624, in restore
DUPLICITY: . restore_get_patched_rop_iter(col_stats)):
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 522, in Write_ROPaths
DUPLICITY: . for ropath in rop_iter:
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 495, in integrate_patch_iters
DUPLICITY: . final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 475, in patch_seq2ropath
DUPLICITY: . misc.copyfileobj( current_file, tempfp )
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/misc.py", line 166, in copyfileobj
DUPLICITY: . buf = infp.read(blocksize)
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py", line 80, in read
DUPLICITY: . self._add_to_outbuf_once()
DUPLICITY: . File "/usr/lib/python2.7/dist-packages/duplicity/librsync.py", line 94, in _add_to_outbuf_once
DUPLICITY: . raise librsyncError(str(e))
DUPLICITY: . librsyncError: librsync error 103 while in patch cycle
DUPLICITY: .

Generally this is the eror I get each time so Iam assuming that it stalls at the same point each time. Any help is appreciated.

Regards

Jim

Question information

Language:
English Edit question
Status:
Expired
For:
Duplicity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Launchpad Janitor (janitor) said : 		#1

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Revision history for this message
edso (ed.so) said : 		#2

what's your duplicity version?

unlikely but possible is that you ran out of tmp space.. this is a bug solved in 0.6.20 where the below mentioned routine didn't respect the
http://duplicity.nongnu.org/duplicity.1.html#sect7
TMPDIR setting.

you can at least try to find a date predating (assuming it is) the corrupt incremental. duplicity essentially recreates the full state and then uses librsync to patch it with each incremental state up to the date you requested to restore.

..ede/duply.net

Revision history for this message
Jim Pearson (kartibok) said : 		#3

Ed,

My Version is duplicity 0.6.19.

I managed to get a backup from the 1st December which will do fine, however I now have a backup testing regime :)

Regards

Jim