[ZODB-Dev] CRC check failed when running repozo

2009-09-14 Thread Chris Withers
Hi All,

Anyone ever see this?

Traceback (most recent call last):
   File /opt/Zope-2.9//bin/repozo.py, line 517, in ?
 main()
   File /opt/Zope-2.9//bin/repozo.py, line 510, in main
 do_backup(options)
   File /opt/Zope-2.9//bin/repozo.py, line 450, in do_backup
 reposz, reposum = concat(repofiles)
   File /opt/Zope-2.9//bin/repozo.py, line 263, in concat
 bytesread += dofile(func, ifp)
   File /opt/Zope-2.9//bin/repozo.py, line 200, in dofile
 data = fp.read(todo)
   File /usr/local/lib/python2.4/gzip.py, line 225, in read
 self._read(readsize)
   File /usr/local/lib/python2.4/gzip.py, line 273, in _read
 self._read_eof()
   File /usr/local/lib/python2.4/gzip.py, line 309, in _read_eof
 raise IOError, CRC check failed
IOError: CRC check failed

Zope 2.9.8...

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing  Python Consulting
- http://www.simplistix.co.uk
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] CRC check failed when running repozo

2009-09-14 Thread Pedro Ferreira
I've sent a mail to this list on 05/26/09 reporting a similar issue.

Regards,

Pedro

Christian Theune wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 On 09/14/2009 10:06 AM, Chris Withers wrote:
   
 Hi All,

 Anyone ever see this?

 Traceback (most recent call last):
File /opt/Zope-2.9//bin/repozo.py, line 517, in ?
  main()
File /opt/Zope-2.9//bin/repozo.py, line 510, in main
  do_backup(options)
File /opt/Zope-2.9//bin/repozo.py, line 450, in do_backup
  reposz, reposum = concat(repofiles)
File /opt/Zope-2.9//bin/repozo.py, line 263, in concat
  bytesread += dofile(func, ifp)
File /opt/Zope-2.9//bin/repozo.py, line 200, in dofile
  data = fp.read(todo)
File /usr/local/lib/python2.4/gzip.py, line 225, in read
  self._read(readsize)
File /usr/local/lib/python2.4/gzip.py, line 273, in _read
  self._read_eof()
File /usr/local/lib/python2.4/gzip.py, line 309, in _read_eof
  raise IOError, CRC check failed
 IOError: CRC check failed

 Zope 2.9.8...
 

 Hmm. Haven't seen that. My guess would be some low-level data corruption.

 Christian

 - -- 
 Christian Theune · c...@gocept.com
 gocept gmbh  co. kg · forsterstraße 29 · 06112 halle (saale) · germany
 http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1
 Zope and Plone consulting and development
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1.4.9 (GNU/Linux)
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAkqt+zAACgkQdUt9X/gknwJ4YwCeMWDYJ4Ap43PFhrnbeQP+ga4Q
 eMYAoKat8o8eIch2DIs4kSsf27A12lgo
 =lQp/
 -END PGP SIGNATURE-
 ___
 For more information about ZODB, see the ZODB Wiki:
 http://www.zope.org/Wikis/ZODB/

 ZODB-Dev mailing list  -  ZODB-Dev@zope.org
 https://mail.zope.org/mailman/listinfo/zodb-dev
   

___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] CRC check failed when running repozo

2009-09-14 Thread Adam GROSZER
Hello,

+1 on that. Sometimes copy operations (over the network) screw up some
bits. Happens rarely but then it hits hard.

Monday, September 14, 2009, 10:13:39 AM, you wrote:

CT Hmm. Haven't seen that. My guess would be some low-level data corruption.

CT Christian



-- 
Best regards,
 Adam GROSZERmailto:agros...@gmail.com
--
Quote of the day:
People are boring unless they're extremists

___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev


Re: [ZODB-Dev] CRC check failed when running repozo

2009-09-14 Thread Chris Withers
Adam GROSZER wrote:
 Hello,
 
 +1 on that. Sometimes copy operations (over the network) screw up some
 bits. Happens rarely but then it hits hard.
 
 Monday, September 14, 2009, 10:13:39 AM, you wrote:
 
 CT Hmm. Haven't seen that. My guess would be some low-level data corruption.
 
 CT Christian

My suspicion is running repozo where the previous repozo run failed and 
the output directory is corrupted.

I'm gonna try blowing away all the previous repozo output and try again...

cheers,

Chris

-- 
Simplistix - Content Management, Batch Processing  Python Consulting
- http://www.simplistix.co.uk
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev