<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000066">
<font size="-1"><font face="Verdana">Wow, the wiki article on Data.fs,
corruption, backup, etc. What a gem,... never saw that before.<br>
<br>
Just wanted to let you know, one question answered helps others.<br>
<br>
Much Appreciated,<br>
<br>
-Jon Cyr<br>
<a class="moz-txt-link-abbreviated" href="mailto:cyrj@cyr.info">cyrj@cyr.info</a><br>
<br>
RE:</font></font>
<pre wrap=""><a class="moz-txt-link-freetext" href="http://zope.org/Wikis/ZODB/FileStorageBackup">http://zope.org/Wikis/ZODB/FileStorageBackup</a></pre>
<font size="-1"><font face="Verdana">. </font></font><br>
<br>
<br>
Tim Peters wrote:
<blockquote cite="mid20040727142807.AF54B3B805B@smtp.zope.com"
type="cite">
<pre wrap="">[shan sverige]
</pre>
<blockquote type="cite">
<pre wrap="">When I try to pack I get:
Error Value: /usr/local/Zope-2.7.0/var/Data.fs:31906881:time-stamp
reduction: 03537a82059cf1cc <= 0355bcc95b5ace33
</pre>
</blockquote>
<pre wrap=""><!---->
Ouch. Looks like the system clock on your machine got set backwards by
about 3 months at some point:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">from ZODB.utils import *
print TimeStamp.TimeStamp(p64(0x03537a82059cf1cc))
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->2004-03-02 17:38:01.315562
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">print TimeStamp.TimeStamp(p64(0x0355bcc95b5ace33))
</pre>
</blockquote>
</blockquote>
</blockquote>
<pre wrap=""><!---->2004-06-12 12:57:21.411260
</pre>
<pre wrap=""><!---->
Then you got bit by this:
<a class="moz-txt-link-freetext" href="http://zope.org/Collectors/Zope/1327">http://zope.org/Collectors/Zope/1327</a>
While no distinct ZODB release was made to correspond with Zope 2.7.2, that
bug should be fixed in Zope 2.7.2. It's still a panic-level problem if the
clock is seen to go backwards by that much, but at least a panic message
will get logged about it now, and FileStorage will force transaction ids to
be monotonically increasing anyway now.
In any case, packing isn't an error recovery procedure. Run the diagnostic
scripts explained here, and start making backups (also explained here):
<a class="moz-txt-link-freetext" href="http://zope.org/Wikis/ZODB/FileStorageBackup">http://zope.org/Wikis/ZODB/FileStorageBackup</a>
</pre>
<blockquote type="cite">
<pre wrap="">After running fsrecover.py the resulting Data.fs can't be mounted. I now
get:
ZODB.POSException.ConflictError: database conflict error
</pre>
</blockquote>
<pre wrap=""><!---->
Sorry, but I bet you have multiple problems in your database now, and
probably stemming from whatever went wrong with your system that caused your
clock to go insane. This could be difficult to recover from. Running
fstest and fsrefs (explained on the page linked to above) will help
determine the extent of the damage.
_______________________________________________
Zope maillist - <a class="moz-txt-link-abbreviated" href="mailto:Zope@zope.org">Zope@zope.org</a>
<a class="moz-txt-link-freetext" href="http://mail.zope.org/mailman/listinfo/zope">http://mail.zope.org/mailman/listinfo/zope</a>
** No cross posts or HTML encoding! **
(Related lists -
<a class="moz-txt-link-freetext" href="http://mail.zope.org/mailman/listinfo/zope-announce">http://mail.zope.org/mailman/listinfo/zope-announce</a>
<a class="moz-txt-link-freetext" href="http://mail.zope.org/mailman/listinfo/zope-dev">http://mail.zope.org/mailman/listinfo/zope-dev</a> )
</pre>
</blockquote>
</body>
</html>