bernhard at intevation.de
Tue May 9 04:16:53 EDT 2006
On Mon, May 08, 2006 at 03:33:11PM -0300, Sergio Devojno Bruder wrote:
> We already saw this 'dying process corrupting skiplist db' a lot, you
> reproduce it with a really big db (>5-7M mailboxes) with little memory
> (<= 1GB) in a linux box easily, some mmap operations will fail ENOMEM
> and the process will give up with a resulting broken db.
> NOTE: mmap will fail with ENOMEM in linux with free memory and lots of
> swap free.
Are you in a position to try our experimental patch for this problem?
See patch.2 attached to https://intevation.de/roundup/kolab/issue840
> We already saw another type of problem with SMP (2 x Xeon with HT, 4
> 'processors' for linux) (Cyrus 2.2.10), resulted in corruption too (and
> all problems with sincronization between frontends, mupdate and
> backends). We "solved" it running a UP kernel on that same box, mupdate
> doesnt need all that cpu power. IE: There is a race there.
Running an SMP linux raised the chances to get a corruption, too.
Is there a chance that this is the same bug,
e.g. a memory locking failure?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : https://lists.andrew.cmu.edu/mailman/private/cyrus-devel/attachments/20060509/bdd69100/attachment.bin
More information about the Cyrus-devel