Hi, My Zope instance (2.6.2) doesn't alert or log anything about ZODB corruption at startup or when browsing, but when I try to compact it, I got this error: Error Type: CorruptedError Error Value: C:\Program Files\Zopista_2_6_1\var\Data.fs:9676045:time-stamp reduction: 0342993b626b50b3 <= 034abe992d2f1aa2 The full traceback is... Traceback (innermost last): Module ZPublisher.Publish, line 98, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 39, in call_object Module App.ApplicationManager, line 353, in manage_pack Module ZODB.DB, line 526, in pack Module ZODB.FileStorage, line 1503, in pack Module ZODB.fspack, line 680, in pack Module ZODB.fspack, line 464, in findReachable Module ZODB.fspack, line 478, in buildPackIndex Module ZODB.fspack, line 175, in checkTxn Module ZODB.fspack, line 170, in fail CorruptedError: C:\Program Files\Zopista_2_6_1\var\Data.fs:9676045:time-stamp reduction: 0342993b626b50b3 <= 034abe992d2f I have tried to run .../lib/ZODB/fsrecover.py utility, but the result is worse than the previous problem: How can I "uncorrupt" that ZODB and compact it again ? Is there another solution than exporting root folderishes and importing them in a clean new instance ? Many thanks in advance for your hints. -- Gilles Lenfant Pilot Systems - 66, rue de Provence - 75009 Paris Tel : +33 1 44 53 05 55 - www.pilotsystems.net Hébergement Zope et Plone gratuit - http://www.objectis.org
Gilles Lenfant wrote at 2004-2-22 20:19 +0100:
My Zope instance (2.6.2) doesn't alert or log anything about ZODB corruption at startup or when browsing, but when I try to compact it, I got this error:
Error Type: CorruptedError Error Value: C:\Program Files\Zopista_2_6_1\var\Data.fs:9676045:time-stamp reduction: 0342993b626b50b3 <= 034abe992d2f1aa2
Apparently, you have had intermittend time problems (your host time jumped backward).
Module ZODB.fspack, line 175, in checkTxn Module ZODB.fspack, line 170, in fail CorruptedError: C:\Program Files\Zopista_2_6_1\var\Data.fs:9676045:time-stamp reduction: 0342993b626b50b3 <= 034abe992d2f
Search the zope and zodb-dev mailing list archive. I think there was a similar problem report with some advice how to fix the problem. -- Dieter
participants (2)
-
Dieter Maurer -
Gilles Lenfant