Hi , Thank you for your reply ! The POSKeyError was solved using the fsrecover.py tool. Zope started, but I was not able to add any kind of information. After som hair pulling, general swearing etc I simply removed all Data.fs related files like Data.fs.lock, Data.fs.in and Data.fs.index and voila: Zope was up and running again. Best regards Petter Enholm ----- Original Message ----- From: "Toby Dickenson" <tdickenson@geminidataloggers.com> To: "Petter Enholm" <pe@snapper.no>; "Zope user list" <zope@zope.org> Sent: Tuesday, May 28, 2002 11:09 AM Subject: Re: [Zope] HELP !! URGENT: POSKeyError
On Monday 27 May 2002 4:18 pm, Petter Enholm wrote:
It seems to me that the Data.fs file is currupted. Is there some way to repair it? The fstest.py tools gives this message:
15570990L object serialno 0x034421cb33bd68f7 does not matchtransaction id 0x034421e30cd63455
If the fstest.py tool is correct in this diagnosis (I have no reason to think it is not, but Ive never used that tool) then this is a failure that 'should not happen'.
I suspect any data after this point may also be corrupt. Can you afford to truncate data.fs at this byte offset, and throw away all subsequent transactions?
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )