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 transaction between two dates? On Thu, Jul 31, 2008 at 4:21 PM, Martijn Pieters <mj@zopatista.com> wrote:
On Thu, Jul 31, 2008 at 10:48 PM, Remy Pinsonnault <remypinsonnault@gmail.com> 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
'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
at 10020462
You have 2 pieces of info there, the oid and the file position. You could use fsdump to verify the oid and position, then truncate the file at that position. Short recipe (may be outdated a bit) of the procedure:
http://kelpi.com/script/018315
I certainly have performed truncations like that in the past.
-- Martijn Pieters