Re: [Evolution] Error Emptying Trash

[Dave Coventry <dcoventry e-zim com>]

Jeff,

I would love to be able to recreate what happened but AFAIK I haven't used any other email client on the 
system apart from Evolution. Mutt or Pine could possibly be operating as a backend to something but I would 
doubt it.

I suspect the discrepency may have been caused by the reiserfs journaling when I had power loss.

I am using Debian (Knoppix installation) on an under-powered laptop 350MHz. I haven't looked at my 'df' for a 
while now, it is possible that I am short of diskspace, I'll check when I get home.

Many thanks,

Dave


--- Jeffrey Stedfast <fejj ximian com> wrote:
On Tue, 2003-10-21 at 23:37, petri kanerva surfeu fi wrote:
[snip]
> Yes it has. And as stated in the other reply, I believe your mailbox
> isn't corrupted.
> My quess is that you deleted the summary file while Evo was running.
> When you close it, it regenerates the corrupted summary. Close evo
> first, then rm the summary, and next time you launch evo, it recreates
> the summary. This will take some time if you have a lot of mails in that
> mbox.
>
> This has worked for me several times. And one reason to get this error,
> is that when expunging mail, evo saves another copy of the mbox file
> without the deleted mails and then deletes the original mbox file. If
> you don't have enough disk space for the new mbox file, this error
> occurs.

uh, I hope not. camel is pretty careful about error checking, so if
there isn't enough disk space left to write the complete (expunged)
mbox, then it will fail and simply not expunge, giving an error dialog.

now, maybe - after expunging the mbox and overwriting the original, if
there isn't enough space on disk for the summary - yes, perhaps the
summary file will get corrupted (although that seems unlikely if you
were able to expunge the mbox which is far larger).

more likely is that the mbox changed on disk behind evolution's back
(ie, the mbox was accessed via mutt or pine, or the user has some
process or another that tries to deliver mail to the mbox when evolution
is running and accessing the folder). We've tried to make it so that
camel handles this gracefully, but there's not much we can do if the
other app isn't properly respecting (and using) file locking.

if you can find a way to reproduce corruption of the mbox file and/or
the summary without the interference of some broken external app, please
provide a detailed bug report.

Jeff

>  Petri
>
>
>
> _______________________________________________
> evolution maillist  -  evolution lists ximian com
> http://lists.ximian.com/mailman/listinfo/evolution


_______________________________________________
evolution maillist  -  evolution lists ximian com
http://lists.ximian.com/mailman/listinfo/evolution


_____________________________________________________________
Get email for your site ---> http://www.everyone.net