Re: upgrading imapd from 3.4.4 to 3.12.1

Hi,

if a new feature or other change in cyrus require additional data to
be stored or other changes to format of the cyrus.* is done the
"max" version is incremented. Between some versions no changes to
the format of the files where made.

Cyrus uses the version of the file read from and write to older version.
This works to some extend, but new feature might not work with old versions.

This step might not be required in your case, but there could be cases  
where the upgrade
step might be skipped/failed for some mailboxes or installation. And  
there is no harm running
it again. So this step is included in all upgrade instructions.








Quoting IMAP List Administration <[email protected]>:

> My previous message was confusing, for which I apologize. What I  
> wanted to say was:
>
> The "reconstruct -V max" pass to upgrade from 3.8 to 3.10 produced  
> one "version 17 to 19" message for each mailbox.
>
> The "reconstruct -V max" pass to upgrade from 3.10 to 3.12 produced  
> nothing and was finished within seconds.
>
> The question is: was the version upgrade pass from 3.10 to 3.12  
> unnecessary, and reconstructed figured this out quickly and exited?
>
> Thanks
>
> On 1/14/26 5:20 PM, IMAP List Administration wrote:
>> after tracing the reconstruct program and looking at the system calls
>> coincident with the "FAILED TO REPACK" message it seemed to have  
>> some problem
>> with the "cyrus.cache" file in the mailbox directory. I deleted this file in
>> the hopes that reconstruct would recreate it, which it seems to  
>> have done, and
>> the "FAILED..." message disappeared.
>>
>> So I guess that is the solution to the problem.
>>
>> After upgrading to 3.10 (running "reconstruct" with "-fG" and then  
>> "-V max"),
>> I performed the same steps to upgrade to 3.12. The reconstruct pass  
>> with "-fG"
>> produced a log message for every mailbox, and in addition exactly  
>> one "rewrote
>> cache..." message, which was encouraging. The pass with "-V max"  
>> seems to have
>> updated every mailbox from version 17 to 19.
>>
>> The pass with "-V max" however, produced absolutely nothing in the  
>> way of log
>> messages, and finished within seconds (exit-status=0). Considering that we
>> have about 50 GB of data in partition-default, how is this  
>> possible? Could it
>> be that the "cyrus.index minor version" did not change from 3.10 to  
>> 3.12, and
>> reconstruct can figure this out without looking at every mailbox?
>>
>
> ------------------------------------------
> Cyrus: Info
> Permalink:  
> https://cyrus.topicbox.com/groups/info/Tfbc92e99a5caeba7-Mb074cfa5c7b9c5eedf4eb93e
> Delivery options: https://cyrus.topicbox.com/groups/info/subscription



-- 
--------------------------------------------------------------------------------
Michael Menge                          Tel.: (49) 7071 / 29-70316
Universität Tübingen                   Fax.: (49) 7071 / 29-5912
Zentrum für Datenverarbeitung          mail: [email protected]
Wächterstraße 76
72074 Tübingen


------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/Tfbc92e99a5caeba7-Mbf1d1f2b6c9a2f7da3b9e6f5
Delivery options: https://cyrus.topicbox.com/groups/info/subscription