[Zope-dev] Coroner's toolkit for zope, or how to figure out what went wrong.

Joachim Werner joe@iuveno.de
Mon, 12 Aug 2002 17:50:40 +0200


Hi!

I know of exactly two cases that could really cause a ZODB loose data: if
you reach the 2GB limit with a Python not compiled for larger files and if
you reach the physical limit of your storage. That is, if your case doesn't
add a third one ...

Have you already tried the usual things, i.e. run fstest.py and/or
fsrecover.py? It's quite unlikely that you'd loose a whole tree, as the data
is not physically stored in trees, but added sequentially. You might have
deleted a tree, but that can be rolled back by getting rid of the ZODB
transaction that did the delete.

Cheers

Joachim Werner

----- Original Message -----
From: "Romain Slootmaekers" <romain@zzict.com>
To: <zope-dev@zope.org>
Sent: Monday, August 12, 2002 5:28 PM
Subject: [Zope-dev] Coroner's toolkit for zope, or how to figure out what
went wrong.


> Yo,
>
> we had a nasty crash of our zope server that we use for a b2b web
> application. The Data.fs ZODB lost a significant amount of data.
>
> At this point, we restored the Data.fs from our last backup and the
> server is back up and running. (breathing relieved)
>
> What worries me is that we have no clue whatsoever on what happened,
> besides the constatation that somehow, somewhere we lost a whole tree of
> objects.
>
> So does anyone have an object browser of the ZODB or some
> tools/procedures on how to find out what went wrong?
>
> I really hope we are not going to lose a lot of sleep because of this.
>
>
> TIA,
>
> Sloot.
>
>
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@zope.org
> http://lists.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope )
>
>