|Subject:||Re: [rdiff-backup-users] CRC Check Failed|
|Date:||Tue, 14 Mar 2006 14:49:04 -0700|
|User-agent:||Mail/News 1.5 (X11/20060309)|
dean gaudet wrote:
On Tue, 14 Mar 2006, dean gaudet wrote:On Tue, 14 Mar 2006, Mike Bydalek wrote:I've been trying to backup for a couple of days now and I'm having some problems that I cannot get around. For some reason, rdiff-backup dies while trying to revert every single time. I've tried to delete the directory on both the server and the client without any luck. At this point, I'm pretty stuck, so any suggestions are highly appreciated.which directory did you delete?
File "/usr/lib/python2.4/gzip.py", line 309, in _read_eof raise IOError, "CRC check failed"can you try running "gzip --test" on all the .gz files from the last failed backup?er if it wasn't clear i meant to do this in dest/rdiff-backup-data... perhaps something like this: find dest/rdiff-backup-data -type f -name \*.gz -print0 \ | xargs -0r gzip --test it could take a while but should do the trick...
Here's the results of that:
$ find server-root/rdiff-backup-data -type f -name \*.gz -print0 | xargs -0r gzip --test
gzip: server-root/rdiff-backup-data/mirror_metadata.2006-03-12T21:46:00-07:00.snapshot.gz: unexpected end of file
Should I delete this file and re-run the backup then?
it's likely rdiff-backup needs to be more graceful in the event that gzip finds a crc error in one of its files... but it'd be nice to verify this is what's causing your problem first. i assume you did have a failed backup for some reason -- power failure or other crash during a backup maybe?
I'm not 100% sure why it died, but yes, it failed for some reason.
|[Prev in Thread]||Current Thread||[Next in Thread]|