[ZCM] [ZC] 1117/ 4 Comment "Packing causes POSKeyError in Zope 2.6.2"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1117 Update (Comment) "Packing causes POSKeyError in Zope 2.6.2"
 Status Pending, Zope/bug critical
To followup, visit:
  http://zope.org/Collectors/Zope/1117

==============================================================
= Comment - Entry #4 by ozone on Jan 14, 2004 6:21 am

I'm seeing the same type of corruption on Zope 2.6.2 with FreeBSD 4.8 (using Python 2.1 with WANT_HUGE_STACK_SIZE).
This seems like a very serious bug.

I haven't yet tried updating to Zope 2.6.3.
________________________________________
= Comment - Entry #3 by CMYanko on Jan 8, 2004 8:52 am

I'm getting a POSKeyError in 2.6.1 on a W2K box without having packed at all. I get it trying to view the content of my portal_workflow tool with an error value of '0000000000012423'
________________________________________
= Comment - Entry #2 by sonnq on Nov 14, 2003 10:34 am

This bug is very serious because you can corrupt Data.fs simply by packing it.

In Zope 2.6.1 when I did the same thing (pack(days=0), and then pack(days=1)), Zope raises FileStorageError: "The database has already been packed to a later time or no changes have been made since the last pack".

In Zope 2.6.1 FileStorage.pack() checks if packing is redundant (by calling _redundant_pack) and raises the exception above, while Zope 2.6.2 does not.

________________________________________
= Request - Entry #1 by Anonymous User on Nov 9, 2003 11:39 am

I've got following error with Zope 2.6.2 on both W2K (always) and RH9 (after several tries):
- pack(days=0) -> OK
- pack(days=1) -> data.fs is truncated!
- restart -> POSKeyError
==============================================================