Re: [rdiff-backup-users] CRC check failed

[Jason Holland]

Thanks for the reply.  I'm unsure how the metadata got corrupt, but
blowing it all away and starting from scratch was the only way to fix the
problem.  We hadn't been backing this up for very long, so the loss was
minimal.

Jason

> >>>>> Jason Holland <address@hidden>
> >>>>> wrote the following on Tue, 11 May 2004 09:34:18 -0500 (CDT)
> >
> > We have a home directory we are backing up with rdiff-backup.  It has
> > about 185,000 files in it, and will continue to grow.  This week, we
> > started to get failures when backing up this directory.  Here is the
> > output from rdiff-backup.  Any ideas what the problem might be?
> >   File "/usr/lib/python2.2/site-packages/rdiff_backup/metadata.py", line
> > 246, in get_next_pos
> ...
> >  File "//usr/lib/python2.2/gzip.py", line 245, in _read_eof
> >    raise ValueError, "CRC check failed"
> > ValueError: CRC check failed
>
> It looks like your metadata file got corrupted somehow, and now
> rdiff-backup can't ungzip it.  It's filename is
> <dest-dir>/rdiff-backup-data/mirror_metadata.<time>.gz.  The corrupted
> one is probably the most recent one.
>
> One quick thing to try would be to move it aside.  However, you may
> lose some metadata, for instance if you not backing up as root, you
> will lose ownership information for that particular backup time since
> the ownership is not also stored in the increments/mirror files
> themselves.
>
> More elaborately, you could try to patch it up yourself.  The metadata
> file is a gzipped text file with a simple format.  But if it corrupted
> it seems likely that the information may not be there to begin with.
>
>
> --
> Ben Escoto
>