[ZODB-Dev] Re: Database Corruption.

Ramon Aseniero ramon.aseniero at tryarc.com
Thu Jul 1 15:31:42 EDT 2004


Hi Jeremy,

I am using Zope 2.6.4, see more info below:

-------------------------------------------------------
Zope Version  (Zope 2.6.4 (source release, python 2.1, linux2), python
2.2.3, linux2)  
Python Version  2.2.3+ (#1, Feb 25 2004, 23:29:31) [GCC 3.3.3 (Debian)]

System Platform  linux2  
SOFTWARE_HOME  /usr/lib/zope/lib/python  
ZOPE_HOME  /usr/lib/zope  
INSTANCE_HOME  /village/zope/default  
CLIENT_HOME  /village/zope/default/var  
Process Id  13067 (1113664432)  
------------------------------------------------------------

Thanks,
Ramon

-----Original Message-----
From: Jeremy Hylton [mailto:jeremy at alum.mit.edu] 
Sent: Thursday, July 01, 2004 5:26 AM
To: Ramon Aseniero
Cc: 'Tim Peters'; jim at zope.com; zodb-dev at zope.org
Subject: RE: [ZODB-Dev] Re: Database Corruption.

On Wed, 2004-06-30 at 20:26, Ramon Aseniero wrote:
> Hi Tim,
> 
> No I don't truncate the data.fs at a random time and size.
> 
> I only time I truncate it is when the database gets corrupted and the
> site crashes, but I followed this instructions
> http://www.zope.org/Members/itamar/CorruptedZODB for truncating the
> data.fs
> 
> Below are more log messages from event.log

It may be helpful to use a low-level utility like fsdump to dump the
entire database and look for patterns there.  One rare but recurring
corruption problem is a big chunk of null bytes getting dropped into the
middle of a data.fs.  That shows up in a very obvious way in the fsdump
output.  The output will also show the dates and classes involved in
transactions, which may provide clues about partially corrupted ones.

Jeremy

PS Did you mention which version of ZODB you are using?







More information about the ZODB-Dev mailing list