[Zope] repozo problem

Dieter Maurer dieter at handshake.de
Tue Jan 24 14:44:54 EST 2006


Gerhard Schmidt wrote at 2006-1-23 10:59 +0100:
>I have some problems with repozo. I have setup repozo for backup of our
>Data.fs about two years ago and it worked without problem until 4 weeks
>ago. Since than it behaves very strange.
>
>I am running repozo with den follwing parameters.
>
>/usr/local/bin/python /usr/local/www/Zope/bin/repozo.py -v -z -B -f /data/zope/zeo/var/Data.fs -r /data/share/backup/data.fs/
>
>and I get the following error.
> ...
>Traceback (most recent call last):
>  File "/usr/local/www/Zope/bin/repozo.py", line 501, in ?
>    main()
>  File "/usr/local/www/Zope/bin/repozo.py", line 494, in main
>    do_backup(options)
>  File "/usr/local/www/Zope/bin/repozo.py", line 431, in do_backup
>    reposz, reposum = concat(repofiles)
>  File "/usr/local/www/Zope/bin/repozo.py", line 248, in concat
>    bytesread += dofile(func, ifp)
>  File "/usr/local/www/Zope/bin/repozo.py", line 192, in dofile
>    data = fp.read(todo)
>  File "/usr/local/lib/python2.3/gzip.py", line 224, in read
>    self._read(readsize)
>  File "/usr/local/lib/python2.3/gzip.py", line 289, in _read
>    self._read_eof()
>  File "/usr/local/lib/python2.3/gzip.py", line 308, in _read_eof
>    raise IOError, "CRC check failed"
>IOError: CRC check failed

Looks as if some of the "concat"ed files is corrupted (as
seen by a wrong CRC checksum).


I would try to discard all incremental backups and make a full
one.

-- 
Dieter


More information about the Zope mailing list