Re: huge mdbox broken / Log synchronization error

2021-05-10 Thread Timo Sirainen
On 7. May 2021, at 16.16, Florian Lohoff wrote: > > On Fri, May 07, 2021 at 09:17:26AM +0200, Florian Lohoff wrote: >> So i am pretty shure nothing else is accessing this mailbox - This morning >> i opened the screen session and i am here: > > Okay - ran doveadm force-resync and it finished wit

Re: huge mdbox broken / Log synchronization error

2021-05-07 Thread Florian Lohoff
On Fri, May 07, 2021 at 09:17:26AM +0200, Florian Lohoff wrote: > So i am pretty shure nothing else is accessing this mailbox - This morning > i opened the screen session and i am here: Okay - ran doveadm force-resync and it finished without further notices. I changed password back and immediatl

Re: huge mdbox broken / Log synchronization error

2021-05-07 Thread Florian Lohoff
On Thu, May 06, 2021 at 02:24:36PM +0300, Aki Tuomi wrote: > Sorry, I ment that it really looks like, based on the logs, that > something else was hoarding your indexes for 15023 seconds, and I > can't really think anything else than some imap process being there. > Or you are running it twice. So

Re: huge mdbox broken / Log synchronization error

2021-05-06 Thread Aki Tuomi
> On 06/05/2021 14:22 Florian Lohoff wrote: > > > On Thu, May 06, 2021 at 02:11:16PM +0300, Aki Tuomi wrote: > > > doveadm(in...@wasteland.rfc822.org): Warning: Transaction log file > > > /var/vmail/wasteland.rfc822.org/inbox/mdbox/storage/dovecot.map.index.log > > > was locked for 15023 se

Re: huge mdbox broken / Log synchronization error

2021-05-06 Thread Florian Lohoff
On Thu, May 06, 2021 at 02:11:16PM +0300, Aki Tuomi wrote: > > doveadm(in...@wasteland.rfc822.org): Warning: Transaction log file > > /var/vmail/wasteland.rfc822.org/inbox/mdbox/storage/dovecot.map.index.log > > was locked for 15023 seconds (rotating while syncing) > > doveadm(in...@wasteland.rfc

Re: huge mdbox broken / Log synchronization error

2021-05-06 Thread Aki Tuomi
> On 06/05/2021 14:09 Florian Lohoff wrote: > > > On Thu, May 06, 2021 at 09:56:48AM +0300, Aki Tuomi wrote: > > > > > > I upgraded to 2.3.4 from stretch-backports now and rerunning force-fsck > > > now. > > > > > This seems to indicate that there is some larger corruption in your mdbox >

Re: huge mdbox broken / Log synchronization error

2021-05-06 Thread Florian Lohoff
On Thu, May 06, 2021 at 09:56:48AM +0300, Aki Tuomi wrote: > > > > I upgraded to 2.3.4 from stretch-backports now and rerunning force-fsck now. > > > This seems to indicate that there is some larger corruption in your mdbox > files. I'm afraid it might mean that you need to rm the dovecot.map.in

Re: huge mdbox broken / Log synchronization error

2021-05-05 Thread Aki Tuomi
> On 06/05/2021 09:54 Florian Lohoff wrote: > > > On Wed, May 05, 2021 at 03:30:39PM +0300, Aki Tuomi wrote: > > Hi! > > > > That version is pretty old already, there has been fixes to mdbox format > > after that. Can you at least try to upgrade to 2.2.36? > > Aborted force-resync after 16

Re: huge mdbox broken / Log synchronization error

2021-05-05 Thread Florian Lohoff
On Wed, May 05, 2021 at 03:30:39PM +0300, Aki Tuomi wrote: > Hi! > > That version is pretty old already, there has been fixes to mdbox format > after that. Can you at least try to upgrade to 2.2.36? Aborted force-resync after 16 hours - Every fsck took 2-3 hours. It always restarted from the beg

Re: huge mdbox broken / Log synchronization error

2021-05-05 Thread Aki Tuomi
> On 05/05/2021 12:42 Florian Lohoff wrote: > > > Hi, > its the second time in 6 Month i have issues with a huge mdbox. It > broken in November and i restored from backup because force-resync > twice didnt fix it. (And restore from borg-backup was MUCH faster > than force-resync) > > This ti

huge mdbox broken / Log synchronization error

2021-05-05 Thread Florian Lohoff
Hi, its the second time in 6 Month i have issues with a huge mdbox. It broken in November and i restored from backup because force-resync twice didnt fix it. (And restore from borg-backup was MUCH faster than force-resync) This time i have heavy delivery into that mailbox (postfix concurrency 1)