dovecot - Jan 2012 - dovecot 2.0.15 - purge errors

Dovecot 2.0.15, debian package, am I lost some mails? How can I check
what is in *.broken file?

--8<---------------cut here---------------start------------->8---
$doveadm -v purge
doveadm(kjonca): Error: Corrupted dbox file /home/kjonca/Mail/0/storage/m.6469
(around offset=291530): purging found mismatched offsets (291500 vs 299692,
60/215)
doveadm(kjonca): Warning: mdbox /home/kjonca/Mail/0/storage: rebuilding indexes
doveadm(kjonca): Error: Corrupted dbox file /home/kjonca/Mail/0/storage/m.6469
(around offset=599914): metadata header has bad magic value
doveadm(kjonca): Warning: dbox: Copy of the broken file saved to
/home/kjonca/Mail/0/storage/m.6469.broken
doveadm(kjonca): Warning: Transaction log file
/home/kjonca/Mail/0/storage/dovecot.map.index.log was locked for 211 seconds
doveadm(kjonca): Error: Purging namespace '' failed: Internal error
occurred. Refer to server log for more information. [2012-01-13 06:45:07]
--8<---------------cut here---------------end--------------->8---



doveconf -n 
--8<---------------cut here---------------start------------->8---
# 2.0.15: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.38+3-64 x86_64 Debian wheezy/sid 
auth_debug = yes
auth_mechanisms = digest-md5 cram-md5 login plain
auth_verbose = yes
listen = alfa
log_path = /var/log/dovecot
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_debug = yes
mail_location = mdbox:~/Mail/0
mail_log_prefix = "%Us(%u): "
mail_plugins = zlib notify acl
mail_privileged_group = mail
namespace {
  hidden = no
  inbox = yes
  list = yes
  location = 
  prefix = 
  separator = /
  subscriptions = yes
  type = private
}
namespace {
  hidden = no
  inbox = no
  list = yes
  location =
mbox:~/Mail/Old:CONTROL=~/Mail/.dovecot/control/Old:INDEX=~/Mail/.dovecot/index/Old
  prefix = "#Old/"
  separator = /
  subscriptions = yes
  type = private
}
passdb {
  args = scheme=PLAIN /etc/security/dovecot.pwd
  driver = passwd-file
}
plugin {
  acl = vfile
  mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename
  mail_log_fields = uid box msgid size
  zlib_save = bz2
  zlib_save_level = 9
}
protocols = imap
service auth {
  user = root
}
service imap-login {
  process_limit = 2
  process_min_avail = 1
}
service imap {
  vsz_limit = 512 M
}
service pop3-login {
  process_limit = 2
  process_min_avail = 1
}
service pop3 {
  vsz_limit = 512 M
}
ssl = no
userdb {
  driver = passwd
}
verbose_proctitle = yes
protocol imap {
  mail_max_userip_connections = 20
  mail_plugins = zlib imap_zlib  mail_log notify acl
}
protocol pop3 {
  pop3_uidl_format = %08Xu%08Xv
}
protocol lda {
  deliver_log_format = msgid=%m: %$
  log_path = ~/log/deliver.log
  postmaster_address = root at localhost
}
--8<---------------cut here---------------end--------------->8---



-- 
Gdyby kto? mia? zb?dny Toshiba G450 - to ch?tnie przejm? ;)
----------------
Biologia poucza, ze je?li ci? co? ugryz?o, to niemal pewne, ze by?a to samica.

On 13.1.2012, at 8.20, Kamil Jo?ca wrote:
> Dovecot 2.0.15, debian package, am I lost some mails? How can I check
> what is in *.broken file?
You can look at the .broken file with text editor for example :)
> --8<---------------cut here---------------start------------->8---
> $doveadm -v purge
> doveadm(kjonca): Error: Corrupted dbox file
/home/kjonca/Mail/0/storage/m.6469 (around offset=291530): purging found
mismatched offsets (291500 vs 299692, 60/215)
299692 - 291500 = 8192 = output stream's buffering size. I guess what
happened is that sometimes earlier Dovecot crashed while it was saving a
message, but it had managed to write 8192 bytes. Now purging notices the extra
8192 bytes and wonders what to do about them, so it starts index rebuild, which
probably adds it as a new message to mailbox.

In future this check probably should be done before appending the next message
to mdbox, so it's noticed earlier and it probably should delete the message
instead of adding a partially saved message to mailbox.
> doveadm(kjonca): Error: Corrupted dbox file
/home/kjonca/Mail/0/storage/m.6469 (around offset=599914): metadata header has
bad magic value
This is about the same error as above.

So, in short: Nothing to worry about. Although you could look into why the
earlier saving crashed in the first place.