Hi,
Using Zope Debug Console, I used a part of the code fsrefs.py to find the
oid's of POSKeyError:
fs = FileStorage(path, read_only=1)
undone = {}
noload = {}
for oid in fs._index.keys():
try:
data, serial = fs.load(oid, )
except (KeyboardInterrupt,
The object is already gone. It's odd that it is in the index.
You can try deleting the object from the index and then saving the
index. You might need to use ZODB 3.9 to do that, as I think __del__
was only recently added to file-storage indexes.
Jim
On Thu, Jul 23, 2009 at 6:57 AM, Rupesh P
Hi Jim,
But I am using ZODB 3.4.4 :( Are there any other options? How can I find
where this invalid object is being referenced?
Will something like packing resolve this?
Thanks,
Roopesh
On Thu, Jul 23, 2009 at 4:45 PM, Jim Fulton j...@zope.com wrote:
The object is already gone. It's odd
http://spamsch.blogspot.com/2009/04/how-to-repair-broken-zodb-poskeyerror.html
-aj
On 23.07.09 12:57, Rupesh P Raj wrote:
Hi,
Using Zope Debug Console, I used a part of the code fsrefs.py to find
the oid's of POSKeyError:
fs = FileStorage(path, read_only=1)
undone = {}
