Remy Pinsonnault wrote at 2008-7-31 15:48 -0500:
For an unknown reason, it seems our data.fs got corrupted last night. In the
event.log I can see the following:
--
2008-07-30T22:51:59 ERROR ZODB.Connection Couldn't load state for 0x086540
Traceback (most recent call last):
File
Thanks Martijn for your answer.
I tried fsdump but it did not work I got a FileStorageFormatError...
Is there any other way I can obtain the needed paramater (position) for the
truncate function where the CorruptedDataError occured?
Another question, is there a way of extracting all data or
On Fri, Aug 1, 2008 at 7:01 PM, Remy Pinsonnault
[EMAIL PROTECTED] wrote:
I tried fsdump but it did not work I got a FileStorageFormatError...
You only get that error if a) the first four bytes of the file are not
'FS21', or b) the file is smaller than 4 bytes. Are you sure you were
trying this
For an unknown reason, it seems our data.fs got corrupted last night. In the
event.log I can see the following:
--
2008-07-30T22:51:59 ERROR ZODB.Connection Couldn't load state for 0x086540
Traceback (most recent call last):
File C:\PloneExt\Zope\lib\python\ZODB\Connection.py, line 704, in
On Thu, Jul 31, 2008 at 10:48 PM, Remy Pinsonnault
[EMAIL PROTECTED] wrote:
For an unknown reason, it seems our data.fs got corrupted last night. In the
event.log I can see the following:
CorruptedDataError: Error reading oid 0x086540. Found
Daniel Rusch writes:
My colleague had a dtml document turn itself into a folder. When we try
to delete it we get a "CorruptedDataError". Any thoughts on how to kill
the offending vermin?
Zope 2.2 contains a "fsrecover.py" in "ZODB".
Alternatively, there is the "tranalyser" product.
