<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>Dear
All,</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>The system clock of
our Zope 2.7 machine accidentally got set to 2009. We noticed this mistake 6
hours later and we decided to set back the clock to 2008.
</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>How does this affect
the integrity of Data.fs ?</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>From our observation
:</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>1. Session write
errors suddenly began to appear</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>2. Data.fs.index
won't grow anymore and its timestamp remained at the time we set back the
clock</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>3. Packing the
database (which was 8 GB at the time) took too long without any signs of any
Data.fs.pack file in the var folder. We decided to restart Zope after a few
minutes.</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>4. There seem to be
some catalog indexing problems as our catalog searches on a certain field
doesn't work as reliably as it did before. We tried reindexing the field and
even the catalog, but it timed out on us (lots of objects in the
database).</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>Has anyone here had
any similar experiences ? How do I go about fixing this ?</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>Using repozo.py last
night, I made a full backup of Data.fs, copied it to a new instance, was able to
create a new Data.fs.index, and eventually succeeded in packing the 8 GB
database to just 2.4 GB. But it took quite a while - like 10 or 15 minutes
before any Data.fs.pack appeared. </FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial size=2>I haven't checked
yet if the catalog indexing problem has gone away.</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2>Regards,</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2>Danny</FONT></SPAN></DIV>
<DIV><SPAN class=808310802-06052008></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=808310802-06052008><FONT face=Arial
size=2></FONT></SPAN> </DIV></BODY></HTML>