>>>>> JonathanSmith <[EMAIL PROTECTED]> >>>>> wrote the following on Mon, 15 Aug 2005 06:45:19 -0400 > > "A regular file was indicated by the metadata, but could not be > constructed from existing increments because last increment had type > None. Instead of the actual file's data, an empty length file will > be created. This error is probably caused by data loss in the > rdiff-backup destination directory, or a bug in rdiff-backup" > > I thought that they might have to do with the upgrade. The backup > did seem to proceed. The next morning when I came back to the PC, I > found this error report: > > File "/usr/lib/python2.4/site-packages/rdiff_backup/metadata.py", line 247, > in get_next_pos > newbuf = self.fileobj.read(self.blocksize) > File "/usr/lib/python2.4/gzip.py", line 224, in read > self._read(readsize) > File "/usr/lib/python2.4/gzip.py", line 272, in _read > self._read_eof() > File "/usr/lib/python2.4/gzip.py", line 308, in _read_eof > raise IOError, "CRC check failed" > IOError: CRC check failed
It looks like there are errors in your destination directory. Perhaps you could check the filesystem it's on for disk problems. Then see which of your rdiff-backup-data/metadata*gz files have been corrupted. -- Ben Escoto
pgpRjk0PdKVuL.pgp
Description: PGP signature
_______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
