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 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: Confirmed 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
