On Mon, Feb 24, 2003 at 10:58:44AM +0100, Stefan Loidl wrote:
You don't mention (but you've probably seen it) that after the first appearance of this corruption additional version based changes not only give this error, but also result in multiple 'bad transaction length' errors. Eg.
__main__.ErrorFound: bad transaction length at 5095413
REALLY now. that is very interesting. i have a zodb that suffered *thousands* of "bad transaction length" and we have never determined the root cause. However, I know that before I was hired: * some work was done in versions * there was some big data-loss disaster related to versions * somebody managed to recover what they needed * it was decreed "we will use no more versions" ;-) * the zodb was never packed ... they just didn't know to do that :-\ I was only able to fix the problems by using fsrecover.py with the -P -t 0 options. I wonder now if there was some lingering version corruption... -- Paul Winkler http://www.slinkp.com