[Dovecot] "Invalid offset returned by binary tree"
Hi,
I'm running 0.99.10 on OpenBSD 3.4/i386, with Squirrelmail as the only client. I recently had dovecot fail with this in syslog:
Sep 10 14:34:55 pirx imap(alisgray): Corrupted index file /home/alisgray/mail/.imap/INBOX/.imap.index: Invalid offset returned by binary tree: 118 Sep 10 14:34:55 pirx dovecot: child 20827 (imap) killed with signal 11
Poking around some, I see that dovecot.org recommends mmap_no_write=yes for OpenBSD... but that option's not implemented in 0.99.10, afaics.
Does the symptom I'm seeing match the expected failure mode of OpenBSD's noncoherent mmap?
I deleted .imap.* (after saving a backup) and that seems to have fixed the problem. I can provide a copy of the bad file for debugging, if necessary.
And of course, if it's a known bug fixed in 1.0-test, I'd be happy to upgrade.
-andy
On 10.9.2004, at 23:21, Andy Isaacson wrote:
I'm running 0.99.10 on OpenBSD 3.4/i386, with Squirrelmail as the only client. I recently had dovecot fail with this in syslog: .. And of course, if it's a known bug fixed in 1.0-test, I'd be happy to upgrade.
OpenBSD has lots of problems with 0.99's indexes. 1.0-tests should help.
On Sat, Sep 11, 2004 at 01:54:38PM +0300, Timo Sirainen wrote:
On 10.9.2004, at 23:21, Andy Isaacson wrote:
I'm running 0.99.10 on OpenBSD 3.4/i386, with Squirrelmail as the only client. I recently had dovecot fail with this in syslog: .. And of course, if it's a known bug fixed in 1.0-test, I'd be happy to upgrade.
OpenBSD has lots of problems with 0.99's indexes. 1.0-tests should help.
Thanks for the reply. I'll try 1.0-test. Since this was the first problem I noticed in 7 months of operation, I don't expect I'll have any further to report, but I will keep an eye on it.
-andy
participants (2)
-
Andy Isaacson
-
Timo Sirainen