9 Mar
2009
9 Mar
'09
1:23 p.m.
Chris Withers wrote at 2009-3-8 12:26 +0000:
Nope, Zope 2.9.8.
In older ZODB versions, this should happen when your clock jumped back into the past.
The clocks on both the storage servers are NTP synched and I'm pretty sure they've not jumped back at any point...
Another (more serious) cause can be a corruption of the storage file. The timestamp is part of the file data -- it the data changes, the timestamps may seem to be out of order. -- Dieter