<div dir="ltr"><div>Thank you for your answer !</div><div><br></div><div>Considering what you said I'll try to enable replication on the new server. If it doesn't work I'll just schedule some downtime, copy the /var/spool/cyrus folder to the new server, install cyrus 3.0.11 from the backports and then upgrade the mailboxes in place.</div><div><br></div><div>We've been using cyrus since 2004 so there's definitely a lot of old mailboxes around and I don't which versions of cyrus were used.<br></div><div><br></div><div>Cheers,</div><div>Adrien<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le dim. 15 sept. 2019 à 00:35, Adrien Remillieux <<a href="mailto:adrien.remillieux@gmail.com">adrien.remillieux@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Date: Fri, 13 Sep 2019 10:20:17 +1000<br>
From: "ellie timoney" <<a href="mailto:ellie@fastmail.com" target="_blank">ellie@fastmail.com</a>><br>
To: <a href="mailto:info-cyrus@lists.andrew.cmu.edu" target="_blank">info-cyrus@lists.andrew.cmu.edu</a><br>
Subject: Re: Possible issue when upgrading to cyrus 3.0.8 using<br>
replication ?<br>
Message-ID: <<a href="mailto:343a16a2-f5a2-4130-aae0-6a4994ab9556@www.fastmail.com" target="_blank">343a16a2-f5a2-4130-aae0-6a4994ab9556@www.fastmail.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
Hi Adrien,<br>
<br>
The replication upgrade path should be okay. In-place upgrades (that
would use the affected reconstruct to bring mailboxes up to the same
version as the server) would get bitten. Whereas if you replicate to a
newer version server, the mailboxes on the replica will be created at
the replica's preferred version already, so you don't need to
reconstruct afterwards.<br>
<br>
If you have messages that would theoretically be affected by this bug in
3.0, you won't be able to replicate them to 3.0 in the first place,
because I think replication won't allow the 0 modseq. If this arises,
I'm not sure how to recover from it and replicate the affected messages,
since 2.4 and 2.5 won't alter the 0 modseq. If it can't replicate them,
it will complain about it, so if you plan for the replication needing
some handholding/restarting, you'll at least be able to identify which
messages are broken in the process, and then figure out how to handle it
once you know the size of the problem?<br>
<br>
Another option, if you want to stick with the Debian packages, would be to skip 3.0.8 and install 3.0.11 from buster-backports (<a href="https://packages.debian.org/buster-backports/cyrus-imapd" rel="noreferrer" target="_blank">https://packages.debian.org/buster-backports/cyrus-imapd</a>),
and then you'll be immune to the problem. Though you still won't be
able to replicate the affected messages to the new server, hmm.<br>
<br>
Cheers,<br>
<br>
ellie<br>
<br>
On Thu, Sep 12, 2019, at 6:50 AM, Adrien Remillieux wrote:<br>
> Hello,<br>
> <br>
> I have a server that I can't update running cyrus 2.5.10 which
contain mailboxes that have existed from 2.3 and earlier (around 300Gb
total). My plan is to update by enabling replication with a new server
running Debian Buster (so cyrus 3.0.8) and then shutting down the old
server. There was a problem when upgrading to 3.x.x with mailboxes
created with cyrus 2.3 or before and that was fixed in 3.0.11 (see <a href="https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html" rel="noreferrer" target="_blank">https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html</a> and <a href="https://github.com/cyrusimap/cyrus-imapd/issues/2839" rel="noreferrer" target="_blank">https://github.com/cyrusimap/cyrus-imapd/issues/2839</a> for the bug report)<br>
> <br>
> Does this upgrade path suffer from the same issue ? I am not
familiar with the inner-workings of cyrus. It appears that the Debian
maintainers have not backported the patch in 3.0.8 (see <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163" rel="noreferrer" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163</a> and I looked at the source code)<br>
> <br>
> Cheers,<br>
> Adrien<br>
> ----<br>
> Cyrus Home Page: <a href="http://www.cyrusimap.org/" rel="noreferrer" target="_blank">http://www.cyrusimap.org/</a><br>
> List Archives/Info: <a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/" rel="noreferrer" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a><br>
> To Unsubscribe:<br>
> <a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" rel="noreferrer" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190913/5ed8a417/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190913/5ed8a417/attachment-0001.html</a>><br>
</div>
</blockquote></div></div>