I'm also seeing this error pop up in the last few days, despite not
making any changes to the backup configuration (using deja-dup).
Thanks Kenneth for the suggestion above about running with the -v9
command.
Is there a way that I could see the exact duplicity backup command
that's triggered by deja-dup? (I'm new to duplicity & deja-dup). Thanks!
Here's my system details:
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
➜ ~ uname -a
Linux ryzen 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
And the error message:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 432, in write_multivol
at_end = gpg.GzipWriteFile(tarblock_iter, tdp.name, globals.volsize)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 446, in
GzipWriteFile
new_block = block_iter.next()
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 523, in
next
result = self.process(self.input_iter.next())
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 195, in
get_delta_iter
for new_path, sig_path in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/diffdir.py", line 286, in
collate2iters
relem2 = riter2.next()
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 2510, in next
tarinfo = self.tarfile.next()
File "/usr/lib/python2.7/tarfile.py", line 2350, in next
self.fileobj.seek(self.offset - 1)
File "/usr/lib/python2.7/gzip.py", line 443, in seek
self.read(1024)
File "/usr/lib/python2.7/gzip.py", line 268, in read
self._read(readsize)
File "/usr/lib/python2.7/gzip.py", line 332, in _read
self._read_eof()
File "/usr/lib/python2.7/gzip.py", line 354, in _read_eof
hex(self.crc)))
IOError: CRC check failed 0x83aebe8 != 0xa6bb597L
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (<type
'exceptions.IOError'>, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), <traceback object at 0x9fe0554>)
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
----------
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
