Odhiambo Washington
2010-Nov-02 13:39 UTC
[Dovecot] mdbox - how do I fix corrupted indexes?
I am unable top pop mail from my server, using mdbox: Nov 02 16:35:08 pop3-login: Info: Login: user=<wash at domain.co.ke>, method=PLAIN, rip=192.168.40.79, lip=192.168.40.252, mpid=36052 Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file /var/spool/virtual/domain.co.ke/wash/mdbox/storage/m.1 (around offset=1941): Ex t refs metadata corrupted: 3861 783856 75/80/75805ed445f1b8b31508dba8d86280a37a74aec1-fabfb11f9f80654ced090000dcbe1dcb Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file /var/spool/virtual/domain.co.ke/wash/mdbox/storage/m.1 (around offset=1941): ui d=5 points to broken data at offset=1911 Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file /var/spool/virtual/domain.co.ke/wash/mdbox/storage/m.1 (around offset=1941): Ex t refs metadata corrupted: 3861 783856 75/80/75805ed445f1b8b31508dba8d86280a37a74aec1-fabfb11f9f80654ced090000dcbe1dcb Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file /var/spool/virtual/domain.ke/wash/mdbox/storage/m.1 (around offset=1941): ui d=5 points to broken data at offset=1911 Nov 02 16:35:09 pop3(wash at domain.co.ke): Warning: mdbox /var/spool/virtual/ domain.co.ke/wash/mdbox/storage: rebuilding indexes Nov 02 16:35:09 pop3(wash at domain.co.ke): Info: Disconnected: Logged out top=0/0, retr=11/5110, del=10/11, size=803031 This process of "rebuilding indexes" is never ending! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!!
On Tue, 2010-11-02 at 16:39 +0300, Odhiambo Washington wrote:> I am unable top pop mail from my server, using mdbox: > > Nov 02 16:35:08 pop3-login: Info: Login: user=<wash at domain.co.ke>, > method=PLAIN, rip=192.168.40.79, lip=192.168.40.252, mpid=36052 > Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file > /var/spool/virtual/domain.co.ke/wash/mdbox/storage/m.1 (around offset=1941): > Ext refs metadata corrupted: 3861 783856 > 75/80/75805ed445f1b8b31508dba8d86280a37a74aec1-fabfb11f9f80654ced090000dcbe1dcbThis is because you used an earlier version of the SiS code, which used a different format for the extrefs metadata. I thought you were only testing it.. You could fix it by manually adding "-" between the size and path. For example above: 3861 783856 - 75/80/75805ed445f1b8b31508dba8d86280a37a74aec1-fabfb11f9f80654ced090000dcbe1dcb> This process of "rebuilding indexes" is never ending!I should do something about this anyway..