Re: [Duplicity-talk] gpg backup corruption

[Jon]

Nicolas Aspert wrote:
> Hello
> 
> I have been experiencing some kind of gpg corruption when performing
> incremental backups. Duplicity now dies with this message each time:

There is a cleanup switch that you can use to clean up garbage left from
aborted sessions. I don't know what it does, exactly, but it may help
you out.

Jon

> 
> Warning, found incomplete backup sets, probably left from aborted session
> Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 482, in ?
>     with_tempdir(main)
>   File "/usr/bin/duplicity", line 477, in with_tempdir
>     fn()
>   File "/usr/bin/duplicity", line 470, in main
>     incremental_backup(sig_chain)
>   File "/usr/bin/duplicity", line 203, in incremental_backup
>     bytes_written = write_multivol("inc", tarblock_iter, globals.backend)
>   File "/usr/bin/duplicity", line 102, in write_multivol
>     globals.gpg_profile,globals.volsize)
>   File "/usr/lib64/python2.4/site-packages/duplicity/gpg.py", line 213,
> in GPGWriteFile
>     data = block_iter.next(bytes_to_go).data
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 407, in next
>     result = self.process(self.input_iter.next(), size)
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 261, in get_delta_iter_w_sig
>     for new_path, sig_path in collated:
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 173, in collate2iters
>     for relem2 in riter2: yield (None, relem2)
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 234, in combine_path_iters
>     refresh_triple_list(triple_list)
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 222, in refresh_triple_list
>     new_triple = get_triple(old_triple[1])
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 211, in get_triple
>     try: path = path_iter_list[iter_index].next()
>   File "/usr/lib64/python2.4/site-packages/duplicity/diffdir.py", line
> 156, in sigtar2path_iter
>     sigtarobj.close()
>   File "/usr/lib64/python2.4/site-packages/duplicity/dup_temp.py", line
> 107, in close
>     assert not self.fileobj.close()
>   File "/usr/lib64/python2.4/site-packages/duplicity/gpg.py", line 139,
> in close
>     self.gpg_process.wait()
>   File "/usr/lib/python2.4/site-packages/GnuPGInterface.py", line 639,
> in wait
>     raise IOError, "GnuPG exited non-zero, with code %d" % (e << 8)
> IOError: GnuPG exited non-zero, with code 131072
> 
> When running with debug output, it always spits a "invalid packet
> (ctb=14)" before crashing.
> 
> I am not sure whether this can be fixed, but I'd like to see the
> possibility to ignore the faulty incremental backup (or remove it) to
> try to recover things. Unless I have missed something, it seems to me
> the only possibility is to perform a full backup again...
> 
> Best regards
> Nicolas
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
> 

-- 
Jon Watson, CD, Linux+
Computer Geek? Read This -> http://www.jonwatson.ca/book