well, fsrecover helped me in a case just like yours. it does more than just cut off Data.fs, it actually repairs records as well. it's not as primitive as you think. just ty it out. make a copy of your Data.fs and run fsrecover.py on it. for me it came back saying "0 bytes truncated" and at first i thought the file had not changed. but it had and fstest did not find problems anymore. jens On Monday, August 5, 2002, at 04:52 , Joachim Werner wrote:
Hi!
Unfortunately fsrecover.py is a bit too "primitive" for that task. It will just handle problems at the very end of the ZODB and cut the ZODB off when it finds an error. That's exactly what I can't do because that would mean that I loose most of my data.
The tool that seems to be missing for the ZODB is something that really fixes a particular broken entry in the ZODB, not just identifies it.
Cheers
Joachim
----- Original Message ----- From: "Dieter Maurer" <dieter@handshake.de> To: "Joachim Werner" <joe@iuveno.de> Cc: <zope-dev@zope.org> Sent: Sunday, August 04, 2002 11:42 PM Subject: Re: [Zope-dev] Corrupt Data.fs: Is there a way of fixing transaction ids?
Joachim Werner writes:
... How can I fix the Data.fs file? Maybe, you can use "fsrecover.py". It lives in the ZODB folder.
Dieter
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )