On ti, 2010-03-09 at 19:07 +0100, Thomas Leuxner wrote:
Am 09.03.2010 um 19:01 schrieb Timo Sirainen:
Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all
mails.
Actually 'm.59' was not rebuilt but it continued with new containers.
Grepping for the content, it
Am 04.06.2010 um 19:38 schrieb Timo Sirainen:
Do you still happen to have the m.59.broken file? I'd like to look at
it. The fixed files' contents are supposed to be preserved..
Unfortunately don't have it anymore, even on backups.
With the latest fix from Mercurial it does not crash anymore. The message shows
empty and the container in question 'm.59.broken' stays in the 'storage' dir.
Is this expected behavior and am I save to delete the broken container, or how
would I clean up the corruption?
Regards
Thomas
On Tue, 2010-03-09 at 16:40 +0100, Thomas Leuxner wrote:
With the latest fix from Mercurial it does not crash anymore. The message
shows empty and the container in question 'm.59.broken' stays in the
'storage' dir. Is this expected behavior and am I save to delete the broken
container, or
On 9.3.2010, at 20.00, Thomas Leuxner wrote:
Am 09.03.2010 um 18:54 schrieb Thomas Leuxner:
Could not resync it to the Inbox but the message is still in 'm.59.broken'
and the source looks undamaged. Any easy way to restore? No biggie if it is
lost, but just out of curiosity, once an
Am 09.03.2010 um 19:01 schrieb Timo Sirainen:
Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all
mails.
Actually 'm.59' was not rebuilt but it continued with new containers. Grepping
for the content, it remained in the broken container only.
Regards
Thomas
Am 09.03.2010 um 19:02 schrieb Timo Sirainen:
I guess this imap session was open while doveadm was running?
You are right.
