On Tue, Sep 09, 2014 at 01:47:43PM +0200, Michal Sojka wrote: > 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. > if you just symlinked the parent folder, i would expect it to just work. i don't know what would happen if you symlinked just the mailboxes (or parts of them).
> > 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. > maybe it crashed. do you use any wrapper script/daemonizer that could have hidden the exit code from the shell? > .journal file is still present in the directory. Is it correct? Can I > remove the file manually? > don't delete it, or you may even lose mails (unless you delete the entire sync state as well). the journals (and .new files) get cleaned up on a clean exit. if it never exits cleanly, the journals accumulate, and it gets slower and slower. > 8 GB RAM and ext4. > that sure sounds like it should be good enough ... i don't know what one could tweak to improve performance. but concentrating on that is the wrong direction anyway. ------------------------------------------------------------------------------ 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
