John Eikenberry wrote:
This is in relation to the thread referred to in the subject:
http://mail.zope.org/pipermail/zope/2003-February/131336.html
We recently came across this same problem, and after a bit of digging I've got it fixed (for us at least).
What I did was comment out the break at around line 576 in ZODB/FileStorage.py. This break was added between versions 2.6.0 and 2.6.1. For grepping purposes, here's a copy of the break and its preceeding comment:
# Once we've found the data we are looking for, # we can stop chasing backpointers. break
Just comment out that break and all should be good to go.
Hi John, I've tried your fix, but unfortunately it didn't fix my problems with versions. After some time using versions my Data.fs gets corrupt (happens with Zope 2.5.1 and Zope 2.6.1). So just one question, did you ever try to run lib/python/ZODB/fsrecover.py on your Data.fs (be aware of overwriting your Data.fs if you haven't used fsrecover.py before)? Even if I only do one change to a DTML Document using a version and save the version afterwards, I always get a: ZODB.POSException.VersionLockError: ("'\\x00\\x00\\x00\\x00\\x00\\x00\\x00T'", '/Test Version') from fsrecover.py. I only get rid of this kind of error by packing the database in the database control panel or by exporting and importing my application. Thanks, Stefan -- Stefan Loidl Phone: +49 89 289 28882 Leibniz Supercomputing Center Fax: +49 89 2809460 Barer Str. 21 mailto:loidl@lrz.de 80333 Munich, Germany http://www.lrz.de