[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
My workaround for this problem: i went to the backupserver where our remote backups are located ls -latr *.sigtar.gz (pick the last one and gave it a "_" as prefix) after that i could do a purge again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Status: Confirmed => Incomplete ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) ** Changed in: duplicity Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Snarky and off topic, but true. I've left this bug open intentionally since it happens on occasion. I don't believe duplicity is at fault. Mostly these kind of errors happen because of: -- Ctrl-C happy users and Python's poor handling of signals. -- Consumer grade electronics with: memory without ECC or parity, routers that have packet confirmation turned off, the occasional hard drive bit rot, or any other factor that makes equipment cheap to buy. Errors are rare but in a high population it's a lot less rare than you might imagine. So, please take your spam and leave it where it belongs, in the bit bucket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Wow, this is so interesting. Almost 10 years old bug, official (!) Ubuntu app for backup, and not fixed yet. Guys, seriously. I highly recommend BordBackup. It is reliable, fast, has an active development (!) and GUI frontend. And yes, it is working on different OS'es. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
This bug just happened on my father's PC and I can provide steps to reproduce: 1. Attempt to back up more files than can be stored onto the backup device 2. Backup fails with "not enough space error" 3. Change the configuration in order to be able to backup 4. Manually start a backup The backup fails with the OP error. Deleting the cache dir does not fix it. As a workaround, I have deleted all *sigtar.gz files from the backup device, and this seems to have fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
It has been a long while since this occurred, except when restoring from an older backup. What produced the zeroes is beyond my guess. Very weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
I have some further details about this bug! Not super positive, but still. First, I'm going to mark bug #676767 a duplicate of this. That's a slightly older bug with the same symptom, and a workaround (of deleting the cache) that doesn't seem to work in all cases. But ultimately, it's indistinguishable from this, so I'll dup it. Second, I was recently helping a user that was affected by this. They were on Ubuntu 14.04 moving to 16.04 (meaning a backup made with duplicity 0.6.23-1ubuntu4.1 and deja-dup 30.0-0ubuntu4.1, trying to restore with duplicity 0.7.06-2ubuntu2 and deja-dup 34.2-0ubuntu1.1). After investigating it with them, we found that many (100s!) of their volume files (size 50mb) were all zeros. That is, not valid gzip files but just a file full of zero-bytes. Other files seemed corrupted in a different way (not valid gzip, but not all zeros either). There were less of these. They did not use encryption. They stopped and resumed the backup a few times. It was altogether a single full backup. I don't know what to do with this information. But there it is. I note that we don't see this often anymore? The latest report here is from 18.04, which would be duplicity 0.7.17-0ubuntu1.1. It may be too optimistic to hope that it's solved now. But certainly less common than it used to be, I think? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
And thus ..
RESTORE FAILED
Failed to read /tmp/duplicity-fuftb7sx-tempdir/mktemp-24n9b1zc-1: (, OSError('CRC check failed 0x8b680b5 != 0x6ee58156',), )
So Deja-Dup can neither create a back-up nor restore one
remind me ..
What is this programme supposed to do ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Sooo...
I ran Deja Dup from a terminal
The only output was
"Gtk-Message: 16:48:40.229: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:48:40.244: Failed to load module "canberra-gtk-module"
until (I'm thinking inevitably)
Failed to read /tmp/duplicity-gjzzxxla-tempdir/mktemp-wkx9qah0-2: (, OSError('CRC check failed 0x940ae478 != 0xf0f01999',), )
But here's a thing.
There isn't a /tmp/duplicity-gjzzxxla-tempdir
Still, I'm sure that back-up software is a priority and that there'll be
some sort of a fix this year.
You'd have to be an idiot to do a re-install without a working back-up
wouldn't you ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Failed to read /tmp/duplicity-7esacbqs-tempdir/mktemp-jfb5sld2-2:
(, OSError('CRC check failed 0x940ae478 !=
0xc3978beb',), )
I haven't a clue about how do run a back-up anymore.
I use Deja-Dup exclusively and don't have spare HDD around to try a different
software.
How long before there's some sort of fix or work-around ?
- I'm not savvy enough to try and run Duplicity (and again there's the storage
problem)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
After running the backup again, I'm now getting this error message:
"UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
37: ordinal not in range(128)".
Unfortunately, I've encountered this several times in the past. Also, I
can no longer see the backup log in the deja-dup gui, only the error
message.
I wonder if there's a log file of the entire backup process, so that I
could at least determine the problematic file(s)?
Here's the full error message:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
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 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37:
ordinal not in range(128)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
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 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
A couple of things to check: - If you run with -v9 you will get a long and detailed log of the run. The individual file that is causing the problem should be listed. Test that file by unzipping and decoding. If it fails, you can delete the incrementals containing it and all subsequent incrementals. You will need to do this in a separate directory so you don't modify the original file. - Check your system logs for "Bad File Descriptor" or other IO errors. A bad file descriptor means that you've run out of descriptors and need to set the limit much higher. This can happen with a long string of incrementals. - Please post the command line you use. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Hi, This bug is affecting me still. $ duplicity --version duplicity 0.7.17 $ apt-cache show duplicity Package: duplicity Architecture: amd64 Version: 0.7.17-0ubuntu1 Priority: optional Section: utils Origin: Ubuntu In the past (129 days ago!) I tried to fix this but got nowhere. Given that the problem persists, perhaps we can debug this together? Where shall I start? How do I get useful debugging out of this for you (obviously I cannot share my mothers data (her machine)). I'm a dev, so complex instructions wont be a problem. Let me know if I can help? (I havent tried to see if its fixed in the development builds of duplicity, since I don't want to accidentally clear the error somehow and remove the ability to reproduce it) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Milestone: 0.7.17 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Milestone: 0.7.16 => 0.7.17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Milestone: 0.7.15 => 0.7.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Status: Confirmed => In Progress ** Changed in: duplicity Milestone: 0.7.14 => 0.7.15 ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Package changed: deja-dup (Ubuntu) => duplicity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** No longer affects: deja-dup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Milestone: 0.7.13.1 => 0.7.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Milestone: 0.7.13 => 0.7.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Milestone: 0.7.12 => 0.7.13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: deja-dup (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Changed in: duplicity Importance: Undecided => High ** Changed in: duplicity Milestone: None => 0.7.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Setting to "Confirmed", because this bug affects multiple users. ** Changed in: deja-dup Status: New => Confirmed ** Changed in: duplicity Status: New => Confirmed ** Changed in: deja-dup Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
There is a disconnect between Ubuntu distribution and upstream distribution
(me). Ubuntu will not, repeat will not, allow changes that add
functionality, or upgrade the version number of a product in a
distribution. I can't live with that, so my distribution version changes
with every release. Before you upgrade manually, apt remove the old
version of duplicity and install from one of the sources below to stay
up-to-date.
Please upgrade to the current version of duplicity. This will assure that
any bugs fixed since your release are available and my fix your issue.
There are three options:
- Release tarball Install - https://launchpad.net/duplicity/+download
- Daily duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily
- Stable duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/ppa
On Mon, Jan 30, 2017 at 8:04 AM, Matej Kovacic <875...@bugs.launchpad.net>
wrote:
> No that it is not good. This is completely irresponsible and lame.
>
> It is a shame, that so important software is a part of core Ubuntu
> system. Canonical should reconsider using it. Because backup is critical
> and if DejaDup is a part of a core system, people rely on it.
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/875676
>
> Title:
> Backing up fails with 'IOError CRC check failed'.
>
> Status in Déjà Dup:
> New
> Status in Duplicity:
> New
> Status in deja-dup 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: ( 'exceptions.IOError'>, IOError('CRC check failed 0x8434f7d2L !=
> 0x3d503338L',), )
>
> 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/deja-dup/+bug/875676/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
No that it is not good. This is completely irresponsible and lame. It is a shame, that so important software is a part of core Ubuntu system. Canonical should reconsider using it. Because backup is critical and if DejaDup is a part of a core system, people rely on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
I think I've got the same problem.
DejaDup with Ubuntu 16.04 prints the same error message and even
duplicity can't do anything in the backup folder. ("remove-older-than"
fails with "(, IOError('CRC check failed
0xb1276c7b != 0x9b944aa5L',), )".)
If I delete or move duplicity-new-
signatures.20160922T090645Z.to.20160929T083644Z.sigtar.gz, it might work
again.
But this is really not good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
I have the same error with DejaDup in Ubuntu 16.04.
I am trying to run a backup (not restore!), and got this error:
Ni mogoče brati /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (, IOError('CRC check failed 0x5528869f !=
0x2aeb4411L',), )
It is in slovenian, but it means:
Cannot read /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (, IOError('CRC check failed 0x5528869f != 0x2aeb4411L',),
)
I tried to delete .cache/deja-dup, but the error is still there.
I am doing a backup to a remote server via ssh. I have reported this
under another bug, but it seems it belongs here.
Anyway, I deleted a file "duplicity-new-
signatures.20161011T065304Z.to.20161013T050922Z.sigtar.gz" on a backup
server, and now it is working (however, it started a new backup). But
this is really bad.
And just another question - would it be possible for me to restore
backup in that case?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: deja-dup (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/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Hello everyone, Is this bug solved?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
Every time I start a backup I get the following error:
Failed to read
/home/user/.cache/deja-dup/tmp/duplicity-7EsAky-tempdir/mktemp-hqHmHI-63:
(type 'exceptions.IOError', IOError('CRC check failed 0x6ae5ab23 !=
0x78b803e5L',), traceback object at 0x7f4f3cfa06c8)
Deleting the cace dir does not help.
This issue showed up since some weeks but apparently I didn't change settings.
I'm using Ubuntu 14.10 with kernel 3.16.0-34-generic
deja-dup 32.0-0ubuntu1.1
duplicity 0.6.23-1ubuntu5
Any clue on solving and debugging?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
** Also affects: deja-dup (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/875676 Title: Backing up fails with 'IOError CRC check failed'. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/875676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
