Re: Cyrus 2.4.9 Released
Rudy Gevaert wrote: > I'm sure I'm not the only one that is appreciating the hard work > Opera is doing on cyrus. > Me too! Me too! Me too! Very glad to have Bron and Greg on board! Kind regards, Jeroen van Meeuwen -- Senior Engineer, Kolab Systems AG e: vanmeeuwen at kolabsys.com t: +44 144 340 9500 m: +44 74 2516 3817 w: http://www.kolabsys.com pgp: 9342 BF08
Re: Cyrus 2.4.9 Released
On Fri, Jun 24, 2011 at 09:12:17PM +0200, Rudy Gevaert wrote: > > Yes, that is quite possible! > > > > I recommend running quota -f twice to fix it, possibly even with the > > server down if you're worried about mail bouncing during the short > > time that quota usage is incorrectly doubled. > > Taking it offline is impossible. Luckily we increased everybodies > quota to 5G some time before. I don't think many will hit that limit. Excellent :) And it will only be for a few minutes. > If I understand you correctly, if I run the quota -f twice the > probably will be totally fixed? Or will it show again, till the bug > is fixed. After running quota -f twice with 2.4.9 the bug is fixed. The 2.4.9 fixed the bug, the quota -f cleans up the old messes. > > I really hope to have a fix to the quota issue soon, and to ship 2.4.10. > > Unfortunately it really needs a complete reworking of the quota tool, > > and also some changes to how lib/cyrusdb_quotalegacy.c handles foreach. > > Then I can fix ALL the outstanding quota related bugs in one big fix :) > > I'm sure I'm not the only one that is appreciating the hard work > Opera is doing on cyrus. :) Thanks, Bron.
Re: Cyrus 2.4.9 Released
Hi Bron, Thanks for you reply. On Fri, Jun 24, 2011 at 06:10:15PM +0200, Bron Gondwana wrote: > > Yes, that is quite possible! > > I recommend running quota -f twice to fix it, possibly even with the > server down if you're worried about mail bouncing during the short > time that quota usage is incorrectly doubled. Taking it offline is impossible. Luckily we increased everybodies quota to 5G some time before. I don't think many will hit that limit. If I understand you correctly, if I run the quota -f twice the probably will be totally fixed? Or will it show again, till the bug is fixed. > I really hope to have a fix to the quota issue soon, and to ship 2.4.10. > Unfortunately it really needs a complete reworking of the quota tool, > and also some changes to how lib/cyrusdb_quotalegacy.c handles foreach. > Then I can fix ALL the outstanding quota related bugs in one big fix :) I'm sure I'm not the only one that is appreciating the hard work Opera is doing on cyrus. Rudy
Re: Cyrus 2.4.9 Released
On 06/24/2011 12:40 PM, Gordon Doell wrote: Is there any reason you are including me in these emails? If not, please stop including me in your email communications. You are included in these emails because you are subscribed to the cyrus-devel mailing list. http://cyrusimap.org/mediawiki/index.php/Cyrus_Mailing_Lists hth, Dave
Re: Cyrus 2.4.9 Released
Is there any reason you are including me in these emails? If not, please stop including me in your email communications. Thank you. - Original Message - From: Bron Gondwana [mailto:br...@fastmail.fm] Sent: Friday, June 24, 2011 10:30 AM To: Rudy Gevaert ; Cyrus Devel Subject: Re: Cyrus 2.4.9 Released On Fri, 24 Jun 2011 17:45 +0200, "Rudy Gevaert" wrote: > On 06/21/2011 11:46 PM, Bron Gondwana wrote: > > > WARNING: if you run quota -f, it can double the used quota value > > for ALL users on your server if it has to fix the quota root on > > any mailbox. > > > > This bug has existed for a long time, but is only found when > > fixing a wrong quota root, hence the likelyhood that you will > > encounter it now if you've been upgrading frequently. The bug > > was unable to be fixed in time for this release, so we > > recommend you use the following workaround. > > > > *** with 2.4.9 (and earlier) ALWAYS run 'quota -f' twice *** > > > > The list of reported bugs fixed can be found here: > > > > http://cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.9 > > > > (or check the changelog for the ones that were actually FIXED in > > this release rather than closed as no-longer-present) > > > > If you want extreme detail of all changes made, check git: > > > > http://git.cyrusimap.org/cyrus-imapd/log/?id=cyrus-imapd-2.4.9 > > > Would the following messages been shown if I have been bitten by this bug? > > > LOSTQUOTA: unable to record quota file ugent.be!user > > I'm seeing many of them in my logs... Yes, that is quite possible! I recommend running quota -f twice to fix it, possibly even with the server down if you're worried about mail bouncing during the short time that quota usage is incorrectly doubled. I really hope to have a fix to the quota issue soon, and to ship 2.4.10. Unfortunately it really needs a complete reworking of the quota tool, and also some changes to how lib/cyrusdb_quotalegacy.c handles foreach. Then I can fix ALL the outstanding quota related bugs in one big fix :) Bron. -- Bron Gondwana br...@fastmail.fm
Re: Cyrus 2.4.9 Released
On Fri, 24 Jun 2011 17:45 +0200, "Rudy Gevaert" wrote: > On 06/21/2011 11:46 PM, Bron Gondwana wrote: > > > WARNING: if you run quota -f, it can double the used quota value > > for ALL users on your server if it has to fix the quota root on > > any mailbox. > > > > This bug has existed for a long time, but is only found when > > fixing a wrong quota root, hence the likelyhood that you will > > encounter it now if you've been upgrading frequently. The bug > > was unable to be fixed in time for this release, so we > > recommend you use the following workaround. > > > > *** with 2.4.9 (and earlier) ALWAYS run 'quota -f' twice *** > > > > The list of reported bugs fixed can be found here: > > > > http://cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.9 > > > > (or check the changelog for the ones that were actually FIXED in > > this release rather than closed as no-longer-present) > > > > If you want extreme detail of all changes made, check git: > > > > http://git.cyrusimap.org/cyrus-imapd/log/?id=cyrus-imapd-2.4.9 > > > Would the following messages been shown if I have been bitten by this bug? > > > LOSTQUOTA: unable to record quota file ugent.be!user > > I'm seeing many of them in my logs... Yes, that is quite possible! I recommend running quota -f twice to fix it, possibly even with the server down if you're worried about mail bouncing during the short time that quota usage is incorrectly doubled. I really hope to have a fix to the quota issue soon, and to ship 2.4.10. Unfortunately it really needs a complete reworking of the quota tool, and also some changes to how lib/cyrusdb_quotalegacy.c handles foreach. Then I can fix ALL the outstanding quota related bugs in one big fix :) Bron. -- Bron Gondwana br...@fastmail.fm
Re: Cyrus 2.4.9 Released
On 06/21/2011 11:46 PM, Bron Gondwana wrote: WARNING: if you run quota -f, it can double the used quota value for ALL users on your server if it has to fix the quota root on any mailbox. This bug has existed for a long time, but is only found when fixing a wrong quota root, hence the likelyhood that you will encounter it now if you've been upgrading frequently. The bug was unable to be fixed in time for this release, so we recommend you use the following workaround. *** with 2.4.9 (and earlier) ALWAYS run 'quota -f' twice *** The list of reported bugs fixed can be found here: http://cyrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.9 (or check the changelog for the ones that were actually FIXED in this release rather than closed as no-longer-present) If you want extreme detail of all changes made, check git: http://git.cyrusimap.org/cyrus-imapd/log/?id=cyrus-imapd-2.4.9 Would the following messages been shown if I have been bitten by this bug? LOSTQUOTA: unable to record quota file ugent.be!user I'm seeing many of them in my logs... Thanks!
