>>> "Jeremy Hylton" wrote
> I don't recall that any of the pack bugs that we fixed caused this sort of
> error. My first guess would be that the file is a bit damaged, perhaps in a
> way that the old pack did not check.
> Can you run fsdump.py and see if that output sheds any light. It will give
Woohoo! Fixed. I created an empty file, then used copyTransactionsFrom
to copy all transactions across. This patched the backpointers. fsrecover.py
should probably get some smarts to do something like this as well, but I've
spent far too long on this problem already... :-/
from ZODB import FileS
, 2003 4:18 AM
> To: [EMAIL PROTECTED]
> Subject: [Zope-dev] Packing (still) hosed in 2.6.2?
>
>
> I remember that 2.6 had issues with packing, but I was under the
> impression that they'd been fixed...
>
> However, attempting to pack a Data.fs in 2.6-current-cvs
I remember that 2.6 had issues with packing, but I was under the
impression that they'd been fixed...
However, attempting to pack a Data.fs in 2.6-current-cvs fails
for me:
File "/export/01/zope/dev_csr_code/lib/python/ZODB/DB.py", line 526, in pack
try: self._storage.pack(t,referencesf)
Anthony Baxter wrote at 2003-8-12 18:18 +1000:
> I remember that 2.6 had issues with packing, but I was under the
> impression that they'd been fixed...
>
> However, attempting to pack a Data.fs in 2.6-current-cvs fails
> for me:
> ...
> raise CorruptedError(s)
> ZODB.fspack.Corrupted