[Dovecot] Corrupted transaction log file / record size too small

[Timo Sirainen]

On Tue, 2008-09-30 at 02:08 -0400, Steven Winikoff wrote:
>    Sep 30 00:09:56 alcor dovecot: pop3[5006] XXXX, NNN.NNN.NN.NNN: Corrupted transaction log file /home/XXXX/.imap/INBOX/dovecot.index.log: record size too small (type=0x40, offset=12224, size=0)
..
> I've been working around the problem by deleting the contents of
> ~user/.imap for affected users, but I'd really prefer to fix it
> properly. :-)  Any suggestions would be gratefully received.

I think this should get fixed by itself? Although the first login fails,
the next one should succeed.

Can you reproduce this by running imaptest (on a test account)?
http://imapwiki.org/ImapTest

Could you apply the attached patch and when it happens for some user
send the saved dovecot.index.broken and dovecot.index.log.broken files
to me? Those files don't contain anything sensitive about the user's
mails. It'll also log a raw backtrace which might show something useful,
so I'd like to see that too (that's only useful if it shows function
names, so debug symbols shouldn't be stripped from the Dovecot
binaries).

I'm not really sure how that error message could happen unless the log
file's contents changed while it was being read.

You could also see if setting mmap_disable=yes makes any difference.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: log-debug.diff
Type: text/x-patch
Size: 1138 bytes
Desc: not available
Url : http://dovecot.org/pipermail/dovecot/attachments/20081005/8c671142/attachment.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20081005/8c671142/attachment-0001.bin