Re: [ZODB-Dev] Persistent ZEO Cache corruption?

2006-01-12 Thread Jim Fulton
Sidnei da Silva wrote: Every now and then I face a corruption of the persistent zeo cache, but this is the first time I get this variant. The cause is very likely to be a forced shutdown of the box this zope instance was running on, but I thought it would be nice to report the issue. Here's

RE: [ZODB-Dev] Persistent ZEO Cache corruption?

2006-01-12 Thread Tim Peters
[Sidnei da Silva] Every now and then I face a corruption of the persistent zeo cache, but this is the first time I get this variant. What other variants do you see? The cause is very likely to be a forced shutdown of the box this zope instance was running on, but I thought it would be nice

RE: [ZODB-Dev] Persistent ZEO Cache corruption?

2006-01-12 Thread Tim Peters
[Tim Peters] ... It doesn't call fsync() unless it's explicitly closed cleanly, but it's unclear what good fsync() actually does across platforms when flush() is called routinely and the power stays on. LOL. Immediately upon sending that msg, there was a power outage here, which left behind

Re: [ZODB-Dev] Persistent ZEO Cache corruption?

2006-01-12 Thread Dennis Allison
I have seen a similar problems bringing up a system which has been brought down with the usual zeoctl stop zopectl start mantra. The zope/zeo connection is via a network connection. Next time it happens I'll file a bug report. On Thu, 12 Jan 2006, Sidnei da Silva wrote: On