Re: Is "reconstruct -V max..." needed when upgrading from 2.5.10 to 3.0.7?

2018-07-31 Thread Savvas Karagiannidis
Oh sorry Nic, didn't notice that it was you on that thread. Then you are probably way ahead of me :) I guess only Bron can answer this then. We had this issue when upgrading large installations and the first one was a real nightmare, costing a night of sleep to bring the system back to operational

Re: Is "reconstruct -V max..." needed when upgrading from 2.5.10 to 3.0.7?

2018-07-31 Thread Nic Bernstein
On 07/31/2018 02:32 PM, Savvas Karagiannidis wrote: Hi Nic, as far as I know there are currently a couple of nasty open issues when upgrading old mailboxes, created from earlier versions of cyrus, that have not been upgraded to v13 index using reconstruct. These issues are:

Re: Is "reconstruct -V max..." needed when upgrading from 2.5.10 to 3.0.7?

2018-07-31 Thread Savvas Karagiannidis
Hi Nic, as far as I know there are currently a couple of nasty open issues when upgrading old mailboxes, created from earlier versions of cyrus, that have not been upgraded to v13 index using reconstruct. These issues are: https://github.com/cyrusimap/cyrus-imapd/issues/2171

Is "reconstruct -V max..." needed when upgrading from 2.5.10 to 3.0.7?

2018-07-31 Thread Nic Bernstein
Friends, I'm preparing for a couple of belated 2.5.X to 3.0.X upgrades, and have a question about how necessary it is to run "reconstruct -V max" on the mailstore.  Both systems are currently running 2.5.10, and are already at index version 13.  However, when performing "reconstruct -V max" on