Re: [rdiff-backup-users] CRC Check Failed

[dean gaudet]

On Tue, 14 Mar 2006, Mike Bydalek wrote:

> 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?

hmm... but no CRC error... odd... i wonder if rdiff-backup requires the 
contents of that file to regress the failed backup.

if you deleted it you might have to do further surgery on the increments 
subdir ... i'm not 100% sure what surgery would be required... but you 
*could* try something like:

        find dest/rdiff-backup-data -name '*.2006-03-12T21:46:00-07:00*' -type 
f -print0 | xargs -0 rm
        find dest/rdiff-backup-data -depth -name '*.2006-03-12T21:46:00-07:00*' 
-type d -print0 | xargs -0 rmdir

which should remove all files created during that backup... that *might* 
leave the mirror in a state where you could perform another backup and 
things would be OK again... but i suspect it will leave some things 
incorrect (been a while since i understood this part of the code).

another option is to lose your increment history entirely -- do "rm -rf 
dest/rdiff-backup-data" and then use the rdiff-backup --force option to 
start again (it'll use the files already in the dest).  i know this method 
works... i've used it many times.

rdiff-backup really needs to handle this one gracefully i think ... it 
should be easy to reproduce by using "kill -9" at random times with an 
in-progress backup (which would be a good regression test anyhow).

-dean