On Tue, Sep 09 2014, Oswald Buddenhagen wrote:
> On Mon, Sep 08, 2014 at 07:25:07PM +0200, Michal Sojka wrote:
>> after moving my maildirs from SSD to rotating disk it takes mbsync very
>> long time (several hours) to load a maildir (mbsync prints "Loading
>> slave..." message). The maildir in question has about 800000 messages. I
>> looked what takes so long and found that mbsync opens every message to
>> search for X-TUID header in it (see the end of maildir_scan() function).
>> 
>> I have two questions:
>> - What is X-TUID good for?
>> - Is it possible to disable opening every message and searching for
>>   X-TUID?
>> 
> these are "temporary UIDs", and mbsync uses them to "bridge an atomicity
> gap" when storing messages. it queries them only if it finds that it
> doesn't have all proper UIDs, which means that the previous run (which
> pulled messages, in your case) didn't terminate cleanly (you should see
> .journal files in the state dir(s)). 

Thanks for quick feedback.

Yes, I have the .journal there. Maybe, I have not correctly moved the
data from one disk to another. I simply moved the maildir and than
created a symlink from the old location to the new one, hoping that
mbsync does not notice the change.

AFAIK mbsync only pay attention to U=nnnn part of the file name and all
files in the maildir seem to have this part.

> if that happens after a clean run, there is something wrong.

I let mbsync run over night and I didn't notice any error message.
.journal file is still present in the directory. Is it correct? Can I
remove the file manually?

> i find it weird *how* slow this is for you. the number only makes sense
> if there are 1-2 seeks for every single file, which would imply that no
> read-ahead whatsoever takes place ... which would be just weird. how
> much ram does the machine have? what file system?

8 GB RAM and ext4.

Cheers,
-Michal

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel

Reply via email to