skiplist db corruption

Martin Konold martin.konold at
Mon Nov 13 03:21:58 EST 2006

Am Montag, 13. November 2006 03:59 schrieb Robert Mueller:

> We still see this every now and then, most often with seen state databases.
> It's most often after an unclean shutdown, but I've seen it at other times
> as well. Has anyone got any more ideas on what might be causing this?

The problem is typically triggered by memory issues (an allocation works 
differently than expected) but also other things can trigger it too.

The memory issues are sofar most likely to occur on Linux but not on *BSD 
according to my experiences.

When restarting (e.g. after the crash) the transaction is not rolled back in 
every case --> corruption.

Workaround: Switch to BDB.

-- martin

Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker

More information about the Cyrus-devel mailing list