On 30.11.2012, at 8.03, Daniel L. Miller wrote:
> Trying to clean up the last of the corruption caused by my own stupidity. I
> now have two mailboxes for one user that give errors such as:
>
> doveadm(f...@amfes.com): Error:
> zlib.read(/var/mail/amfes.com/fax/mdbox/storage/m.9): gz trailer h
Trying to clean up the last of the corruption caused by my own
stupidity. I now have two mailboxes for one user that give errors such as:
doveadm(f...@amfes.com): Error:
zlib.read(/var/mail/amfes.com/fax/mdbox/storage/m.9): gz trailer has
wrong CRC value at 20065618
doveadm(f...@amfes.com): E
On 15.8.2012, at 23.01, 3.lis...@adminlinux.com.br wrote:
> I have a "ubuntu10.04 + ext4-filesystem + dovecot-2.0.13 +mdbox"
> configuration in my server. It works fine with ~50k accounts.
> Recently happened a filesystem corruption in a device of StMailLocation and I
> fix with fsck.ext4.
> Aft
Hi,
I have a "ubuntu10.04 + ext4-filesystem + dovecot-2.0.13 +mdbox"
configuration in my server. It works fine with ~50k accounts.
Recently happened a filesystem corruption in a device of StMailLocation
and I fix with fsck.ext4.
After this crash, one account began to show access timeout and err
On 2.5.2012, at 20.27, Daniel L. Miller wrote:
> I have isolated the corruption in a mailbox to 4 mdbox files. Two of these
> (smaller) files cause the force-resync to report a breakage and save the file
> as m.XX.broken. The other two (larger) files cause a crash.
>
> Is there a way I can fi
I have isolated the corruption in a mailbox to 4 mdbox files. Two of
these (smaller) files cause the force-resync to report a breakage and
save the file as m.XX.broken. The other two (larger) files cause a crash.
Is there a way I can fix these files and recover the mails?
--
Daniel
