[Dovecot] Corrupted Transaction Log File: v1.0.7

[Timo Sirainen]

On Fri, 2007-12-07 at 14:33 +0000, Daniel Watts wrote:
> Following errors have happened quite a bit:
> 
> Dec  7 14:19:26 locallog at tg3/tg3 dovecot: IMAP(peter.day at mydomain.com): 
> Transaction log file 
> /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log: 
> marked corrupted
> 
> Dec  7 14:19:26 locallog at tg3/tg3 dovecot: IMAP(peter.day at mydomain.com): 
> Transaction log file 
> /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log.2: 
> marked corrupted

These happen because of another error that caused them to be marked
corrupted.

> Dec  7 14:19:26 locallog at tg3/tg3 dovecot: IMAP(peter.day at mydomain.com): 
> Corrupted transaction log file 
> /home/virtual/mydomain.com/home/peter.day/Maildir/.Trash/dovecot.index.log: 
> Append with UID 50, but next_uid = 15870

This is the real error. What kind of a system do you have? Do you use
NFS or other shared filesystem? Post your dovecot -n output?

> Shouldn't Dovecot be able to recover from this? 

It does, that's why there are those "marked corrupted" errors. But it
probably does cause the current operation to fail. v1.1 handles this by
logging the error but continuing anyway, so the operation shouldn't
fail.

If you mean that it repeatedly fails with the same error, then the same
error condition is created over and over again for some reason.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://dovecot.org/pipermail/dovecot/attachments/20071207/1e5b7bdd/attachment.bin