On Thu, 14 Oct 2010 17:37:45 +0100 Timo Sirainen <[email protected]> wrote:
> On Fri, 2010-10-08 at 23:51 +0200, Bjørn T Johansen wrote: > > We had to move our dovecot from one server to another and used rsync to > > move the mail but it took us some time.. > > I guess you mean you ran it while users could still be making changes? > > > 2010/10/08 23:28:23 imap(emailadr): Error: Index > > /opt/vmail/ba-avis.no/bpe/mail/.Nettforum/dovecot.index: Lost log for > > seq=22 offset=25248 > > 2010/10/08 23:28:23 imap(emailadr): Warning: fscking index file > > /opt/vmail/ba-avis.no/bpe/mail/.Nettforum/dovecot.index > > Those should go away automatically. Don't worry about them. > > > Also getting a lot of these..: > > > > 2010/10/07 09:12:49 imap(emailadr): Warning: Fixed a duplicate: > > /opt/vmail/ba-avis.no/ihv/mail/cur/1283793654.M548656P18945.pat,W=3656:2,RS > > -> 1286435569.M468796P1301.hostname > > 2010/10/07 09:12:49 imap(emailadr): Warning: Fixed a duplicate: > > /opt/vmail/ba-avis.no/ihv/mail/cur/1285324810.M197070P12420.pat,W=2857:2,Sb > > -> 1286435569.M468797P1301.hostname > > Message's flags were changed between two rsyncs, so the same message got > transferred twice but with different filenames. Dovecot now created a > duplicate message (since it thought that it's safer to create a > duplicate than to delete a non-duplicate). > > > Those are just warning but should I do something with these as well? > > They go away automatically too. Users might be annoyed at the duplicate > messages. > > > And more like these..: > > All of the index errors will go away too. > > > 2010/10/07 23:00:25 imap(emailadr): Panic: file index-status.c: line 155 > > (index_storage_get_status): assertion failed: (status_r->recent <= > > status_r->messages) > > I should some day try to fix this I guess.. > > > BTW, when moving from old server to new we upgraded Dovecot from 1.2.x to > > 2.0.5... > > The next time you could do it with dsync to avoid these kind of > problems. > Yes, it was run while users were making changes... But I discoverd the main reasons for this... Someone had started the rsync process again after we had started using the new server, which kind of "made a mess" of the mails on our new server.... :( But dsync will be tried next time, thx... :) Regards, BTJ
