Re: [Evolution] MailDir + unSYNC + Invalid Root on Evo 1.4.6

[Ow Mun Heng <Ow Mun Heng wdc com>]

On Tue, 2004-10-26 at 19:12, Not Zed wrote:
> The hangs - i have no idea unless you provide backtraces of where it's
> hanging.  A "long delay" isn't a hang either.

It's a complete shutdown. I did provide the traces, Not backtraces using
gdb though. Does the below count?

-----------This is written on xterm------------

olution:21522): camel-WARNING **: Encountered Windows charset parading as iso-8859-1
(evolution:19956): GLib-GObject-WARNING **: gsignal.c:1738: instance `0x852cd978' has no handler with id 
`13595'
(evolution:19974): camel-WARNING **: Could not find key entry for word 'earned': Bad file descriptor
camel-ERROR **: file camel-partition-table.c: line 897 (camel_key_table_lookup): assertion failed: (index < 
kb->used)
aborting...
Xlib: unexpected async reply (sequence 0xc6fda)!
Then it crashes
-------------------------------------------------------

> The warnings about the invalid root/unsync should only happen if
> evolution is crashing or being terminated *while* a body-content index
> is being generated.  e.g. while getting mail, or at the start when
> it's rebuilding.  If this is not the case - then it's possibly
> filesystem issues.  But there are bugs in the indexing code too,
> although they usually manifest themselves in different ways.

Yeah.. As I've used it more, I noticed that that's the exact thing
that's happening. It usually happens when I try to apply filters on my
inbox (/var/spool/mail/user) to get evo to copy/move the messages to
local folder.

> If you can live with slow 'message contains' searches, just turn off
> body indexing altogether, things will run faster, unless you want to
> do a body search in which case they wont.

So.. That's the usage of the "Index-body content" I'll have to think If
that's needed.

> Maildir will only speed up 2 things in evolution if everything is
> working normally:
> - expunging deleted messages
> - if you use colours/labels a lot, since mbox saves them to the actual
> mail file as well as the summary file.
One reason I want to go to MailDir is the long time it takes for the
expunging to happen. Even on XFS, expunging and then building up the
500+MB file takes a long time.
> Otherwise it wont really be any different, and in some cases may be
> slower.  e.g. it's much more involved to check a directory for new
> files than it is to just check the end of a big file for new content.
Well, It seems to draw the line at 40,000 emails. :-)