[ZODB-Dev] More ZODB POSKeyErrors with 2.6.0

[Jeremy Hylton]

>>>>> "CW" == Chris Withers <chrisw@nipltd.com> writes:

  CW> Well, two out of the threee storages produced no output from
  CW> fsrefs.py. The last one spewed out this:

  CW> oid 0x4ab64 failed to load Traceback (most recent call last):
  CW>    File "fsrefs.py", line 67, in main
  CW>      data, serial = fs.load(oid, "")
  CW>    File
  CW>    "/usr/local/zope/2.6.0_cvs_19.09.02/lib/python/ZODB/FileStorage.py",
  CW> line 619, in load
  CW>      return self._load(oid, version, self._index, self._file)
  CW>    File
  CW>    "/usr/local/zope/2.6.0_cvs_19.09.02/lib/python/ZODB/FileStorage.py",
  CW> line 614, in _load
  CW>      return _loadBack(file, oid, pnv)[0], serial
  CW>    File
  CW>    "/usr/local/zope/2.6.0_cvs_19.09.02/lib/python/ZODB/FileStorage.py",
  CW> line 2116, in _loadBack
  CW>      raise POSKeyError(oid)
  CW> POSKeyError: 000000000004ab64

  CW> What does this mean?

It means that this storage has an unloadable object.  I guess you
should actually run fsrefs.py after deleting the index file to be sure
the problem isn't in the index.

  CW> Is it related? (Doesn't appear to be, different OIDs...)

Is this all the output it produced?  I would expect there to be at
least one reference to 0x04ab64 from some other object.

Jeremy