Adam GROSZER wrote:
> +1 on that. Sometimes copy operations (over the network) screw up some
> bits. Happens rarely but then it hits hard.
> Monday, September 14, 2009, 10:13:39 AM, you wrote:
> CT> Hmm. Haven't seen that. My guess would be some low-level data corruption.
> CT> Christian
My suspicion is running repozo where the previous repozo run failed and
the output directory is corrupted.
I'm gonna try blowing away all the previous repozo output and try again...
Simplistix - Content Management, Batch Processing & Python Consulting
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org