Unfortunaltly the clock was set back on one server. Now I get this during pack:
Traceback (most recent call last):
File "/home/user/app/scripts/cron/pack.py", line 77, in ?
File "/home/user/app/scripts/cron/pack.py", line 67, in main
line 815, in pack
return self._server.pack(t, wait)
line 79, in pack
self.rpc.call('pack', t, wait)
line 372, in call
raise inst # error raised by server
/home/user/app/var/data.fs:299901427:time-stamp reduction: 035c9d4907706f44 <=
Version is ZODB 3.2.1.
A search with google for "zodb timestamp reduction" reveals this thread:
Now I know that using fsrecover is a bad idea, since it drops transaction with
Is "copyTransactionsFrom()" the right thing?
Should I use the latest 3.2.x or 3.3. release to try to fix this?
There are backups. The application seems healthy since the daily unittest does
PS: I tried to get timestamps from the tids (035c9d4907706f44), but did not
find a suitable method in ZODB.utils. How long is the clock screw?
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org