Hi,

we are running a cluster using mdbox on NFS with director+mailbox on each node.

After running our daily doveadm purge loop over all users, we got dbox corruption...

doveadm user "*" |
while read username do doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -u "$username" done

For one user (which deleted a lot of messages from his mailboxes today), we got the following error in the dovecot.log:

Jul 22 20:10:36 10.129.3.213 dovecot: doveadm(user@example.org): Error: Corrupted dbox file /mail/dovecot/example.org/user/mail/storage/m.24 (around offset=1380859): purging found mismatched offsets (1380829 vs 920527, 3/61) Jul 22 20:10:36 10.129.3.213 dovecot: doveadm(user@example.org): Warning: mdbox /mail/dovecot/example.org/user/mail/storage: rebuilding indexes

What does this message exactly tell me and how to prevent this in the future?

Now the indexes are broken and flags are lost.

The "storage" directory content of the affected user looks as follows:

drwx------ 2 vmail vmail 4096 2012-07-22 20:10 . drwx------ 4 vmail vmail 4096 2012-05-06 12:16 .. -rw------- 1 vmail vmail 99008 2012-07-22 20:10 dovecot.map.index -rw------- 1 vmail vmail 33016 2012-07-22 20:10 dovecot.map.index.log -rw------- 1 vmail vmail 34664 2012-07-22 20:10 dovecot.map.index.log.2 -rw------- 1 vmail vmail 8134 2012-05-16 11:36 m.22 -rw------- 1 vmail vmail 10572466 2012-06-02 23:09 m.24 -rw------- 1 vmail vmail 1380205 2012-05-27 10:59 m.24.broken -rw------- 1 vmail vmail 6506837 2012-06-09 15:42 m.25 -rw------- 1 vmail vmail 18201641 2012-06-17 22:50 m.26 -rw------- 1 vmail vmail 11345293 2012-07-01 14:37 m.28 -rw------- 1 vmail vmail 36707787 2012-07-08 23:05 m.29 -rw------- 1 vmail vmail 6062419 2012-07-15 23:34 m.30 -rw------- 1 vmail vmail 52396198 2012-07-22 20:10 m.31 -rw------- 1 vmail vmail 3067862 2012-07-20 14:31 m.32 -rw------- 1 vmail vmail 44520965 2012-07-20 14:31 m.33 -rw------- 1 vmail vmail 52426605 2012-07-22 20:10 m.34 -rw------- 1 vmail vmail 28984844 2012-07-22 20:10 m.35 -rw------- 1 vmail vmail 14465248 2012-07-22 20:10 m.36 -rw------- 1 vmail vmail 37451127 2012-07-22 20:10 m.37 -rw------- 1 vmail vmail 41494033 2012-07-22 20:10 m.38 -rw------- 1 vmail vmail 52066924 2012-07-22 20:10 m.39 -rw------- 1 vmail vmail 49785529 2012-07-22 20:10 m.40 -rw------- 1 vmail vmail 23509886 2012-07-22 20:10 m.41 -rw------- 1 vmail vmail 29339462 2012-07-22 20:10 m.42 -rw------- 1 vmail vmail 29510420 2012-07-22 20:10 m.43 -rw------- 1 vmail vmail 50896380 2012-07-22 20:10 m.44 -rw------- 1 vmail vmail 8331046 2012-07-22 20:10 m.45 -rw------- 1 vmail vmail 5903744 2012-07-22 20:10 m.46 -rw------- 1 vmail vmail 70281 2012-07-22 20:10 m.47 -rw------- 1 vmail vmail 27397909 2012-07-22 20:10 m.48 -rw------- 1 vmail vmail 3893509 2012-07-22 20:10 m.49 -rw------- 1 vmail vmail 1410097 2012-07-22 20:10 m.50 -rw------- 1 vmail vmail 1905759 2012-07-22 20:10 m.51 -rw------- 1 vmail vmail 51783968 2012-05-06 12:12 m.9

Any hints on how to prevent dbox corruption in this case? And what should I do with the "m.24.broken" file now?

Regards Daniel

https://plus.google.com/103021802792276734820