[Kolab-devel] [issue805] annotate.db corruptions

[Bernhard Reiter]

New submission from Bernhard Reiter <bernhard at intevation.de>:

There are reported annotate.db corruptions 
where the usual recovery does not help.
AFAIK the cryus imapd does regular recoveries anyway,
so once imapd does not start because of annotate.db,
there is no recovery command to help.

What worked once
was to use 
skiplist.py from http://oss.netfarm.it/python-cyrus.php 
to turn the broken database in a flat file and then
try to convert it to skiplist with cvt_cyrusdb.
My attempt to also do this was not successul because cvt_cyrusdb then failed.

man imapd.conf only gives the choice of skiplist or berkeley for this database
and I am not sure that berkley will be more reliable.
Given that the other skiplist databases have not been seen corrupted,
this might be a problem with the annotate or annotate-more code after all.

This does not occurr very often, but if it would be would need to solve it.
How shall we procede?

Bernhard

----------
messages: 4930
nosy: bernhard, bh, martin, steffen
priority: bug
status: unread
title: annotate.db corruptions
topic: server
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue805>
________________________________________________