Upgrade report debian cyrus

[Savvas Karagiannidis]

Thanks for clarifying this Ellie, I thought the two issues are actually
related.
And thanks for adding the mention to -G to the release notes.

Regards,
Savvas Karagiannidis

On Mon, Aug 5, 2019 at 3:22 AM ellie timoney <ellie at fastmail.com> wrote:

> On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer <l.schimmer at cgv.tugraz.at>
> wrote:
>
> and on second run it did find a lot of mails with "reappending" messages.
>
>
> Actually, this sounds like this bug:
> https://github.com/cyrusimap/cyrus-imapd/issues/2839 (fixed last week in
> 3.0.11)
> There is a Debian report for it too:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163
>
> I guess we're going to see a lot of this here, as people start upgrading
> older systems to the new Debian stable and getting Debian's 3.0.8 instead
> of whatever they had before.
>
>
> On Fri, Aug 2, 2019, at 12:44 AM, Savvas Karagiannidis wrote:
>
> there was an issue when upgrading to 3.0.x from older versions (2.x). The
> issue is this:
> https://github.com/cyrusimap/cyrus-imapd/issues/2208
>
> Ellie explains the exact issues with old mail in the last comment before
> closing the issue mentioned above and I'm surprised to not see any mention
> of this (the -G parameter) in the 3.0 release notes and upgrade
> instructions...
>
>
> Oh, I'd forgotten about that! I'm going to add a note about this to the
> reconstruct -G documentation as well as the upgrade notes.
>
> It is a different issue though: the impact of #2208 (since the crash was
> fixed in 3.0.8, anyway) is being unable to replicate due to missing
> GUID's.  You need reconstruct with -G before upgrading if you plan to build
> a new server and replicate your old store to it (which you will find out
> when you try to replicate).  But it won't affect in-place upgrades until
> you try to replicate them somewhere later.
>
> #2839 is rather more annoying because it affects in-place upgrades and
> copy-files-and-reconstruct upgrades!
>
> Cheers,
>
> ellie
>
> On Fri, Aug 2, 2019, at 12:44 AM, Savvas Karagiannidis wrote:
>
> Hi Lars,
> there was an issue when upgrading to 3.0.x from older versions (2.x). The
> issue is this:
> https://github.com/cyrusimap/cyrus-imapd/issues/2208
>
> From my experience, the only way to safely upgrade to 3.0 was to run
> reconstruct -G -V max on all mailboxes while still in the older version.
> Ellie explains the exact issues with old mail in the last comment before
> closing the issue mentioned above and I'm surprised to not see any mention
> of this (the -G parameter) in the 3.0 release notes and upgrade
> instructions...
> You can still run reconstruct -G -V max on the new system with the latest
> version but the result will probably be that these older messages will
> appear as unread.
>
>
> Regards,
> Savvas Karagiannidis
>
> On Thu, Aug 1, 2019 at 5:13 PM Lars Schimmer <l.schimmer at cgv.tugraz.at>
> wrote:
>
> Hi!
>
> Just upgraded my old debian cyrus 2.4.16-4+deb7u2 to cyrus 3.0.8-6.
> I did use a new hardware system for this, copied over all mailbox,
> sieve,.. data and did a recontruct.
>
> It seems the reconstruct needs a few uns to reconstruct our 100GB mail
> archive (in ~120 mailboxes).
>
> I did a reconctruct -V max and it did not find all mails, I did run it
> twice, and on second run it did find a lot of mails with "reappending"
> messages.
>
> Also, after migration, some users did not seem to have a inbox, I needed
> to "cm user.xcy" and copy mailbox data into it and recontruct manually.
> (seems like those are new mailboxes and are not in the copied data of
> main cyrus db).
>
> But some mailboxes were existent, but empty after the 2 reconstruct (and
> quota) run, I did explicit run reconstruct -r -f user.xyyya on those.
> To bad they got all mails as unseen.
>
> On the most accounts all worked fine, but all mails prior to sept 2011
> are set to unseen.
> Seems like some change of dataformat, as I did upgrade in sept 2011 :-)
>
> Now I sit here and wait for more error reports from the users.
>
>
>
> MfG,
> Lars Schimmer
> --
> -------------------------------------------------------------
> TU Graz, Institut für ComputerGraphik & WissensVisualisierung
> Tel: +43 316 873-5405       E-Mail: l.schimmer at cgv.tugraz.at
> Fax: +43 316 873-5402       PGP-Key-ID: 0x4A9B1723
>
>
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
>
>
> ----
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20190805/a28057e9/attachment-0001.html>