[ZODB-Dev] RE: Database Corruption.

[Ramon Aseniero]

Hi Jim,

I am frequently getting a database corruption on my zope production
environment. I am running Zope 2.6.x on a debian environment. Below is
the error dump from the event.log file.

--------------------------------------dump---------------------
------
2004-06-28T18:02:30 ERROR(200) ZODB Couldn't load state for
'\x00\x00\x00\x00\x00\x02y\x89'
Traceback (innermost last):
  File /usr/lib/zope/lib/python/ZODB/Connection.py, line 551, in
setstate
  File /usr/lib/zope/lib/python/ZODB/FileStorage.py, line 645, in load
    (Object: /village/zope/default/var/Data.fs)
  File /usr/lib/zope/lib/python/ZODB/FileStorage.py, line 623, in _load
    (Object: /village/zope/default/var/Data.fs)
error: unpack str size does not match format
------
2004-06-28T18:02:42 ERROR(200) ZODB Couldn't load state for
'\x00\x00\x00\x00\x00\x03\x02L'
Traceback (innermost last):
  File /usr/lib/zope/lib/python/ZODB/Connection.py, line 551, in
setstate
  File /usr/lib/zope/lib/python/ZODB/FileStorage.py, line 645, in load
    (Object: /village/zope/default/var/Data.fs)
  File /usr/lib/zope/lib/python/ZODB/FileStorage.py, line 623, in _load
    (Object: /village/zope/default/var/Data.fs)
error: unpack str size does not match format
------
--------------------------------------end dump-----------------

-----Original Message-----
From: Jim Fulton [mailto:jim at zope.com] 
Sent: Wednesday, June 30, 2004 6:56 AM
To: Ramon Aseniero
Subject: Re: Database Corruption.

Ramon Aseniero wrote:
> Hi All,
> 
>  
> 
> Is there a way to prevent the Zope database from being corrupted?

I assume you are refering to ZODB. If so, this is the wrong list.
This list is about using Zope with relational databases. Questions
like this should be posted to zodb-dev at zope.org.

Any database can become corupted due to system or hardware failures.
We've had Sybase databases get corrupted and had customers
with systems so screwed up that their ZODB databases were routinely
corrupted. We knew it was a system problem because tar files they
created to save the bad databases were themselves corrupted.

As a general rule, I would avoid using ZODB (or any other non-trivial
database) with network file systems.

AFAIK, we don't have any outstanding corruption problems due to
software problems.  There were was a packing bug introduced in
ZODB 3.1.2 and ZODB 3.2 that was fixed in ZODB 3.1.5 and ZODB 3.2.1.
This could cause logical corruption (records are ok, but data are
missing),
but not corruption of the database records.

Are you having a problem with corruption?  If so, could you give
some information about the problem? If so, please follow up to
zodb-dev at zope.org.

Jim


-- 
Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org