Removing quotas in 2.3.1 broken?
Simon Matter
simon.matter at ch.sauter-bc.com
Tue Feb 14 03:19:10 EST 2006
> Greets.
>
> I'm having problems removing quotas in Cyrus 2.3.1. I'm using Simon's
> 2.3.1-2 RPM. It looks like the command attempts to remove the mailbox
> quota but instead ends up doing something else. What I'm not sure of so
> lots of logs and details provided:
>
> Before starting I run quota -f to make sure everything is sane:
>
>> bash-3.00$ /usr/lib/cyrus-imapd/quota -f
>> Quota % Used Used Root
>> 600000 0 0 user.drfickle
>> 600000 0 4120 user.lnxgeek
>> 600000 0 0 user.osubeav
>> 800000 0 7 user.scottrus
>
> Using cyradm I look at the existing quota for user.scottrus, remove it,
> then look at it again.
>
>> [root at imap-test users]# cyradm --user cyrus localhost
>> Password:
> >
>> localhost.localdomain> lq user.scottrus
>> STORAGE 7/800000 (0.000875%)
> >
>> localhost.localdomain> sq user.scottrus none
>> remove quota
> >
>> localhost.localdomain> lq user.scottrus
>> /
>> localhost.localdomain> quit
>
> The last listquota command above returns odd results. I would expect to
> see blank line as with mailboxes that have been created without a quota
> limit set.
>
> Looking at the trace though everything looks okay:
>
>> <1139867718<4 RLIST "" ""
>>>1139867718>* LIST (\Noselect) "." ""
>> 4 OK Completed (0.000 secs 0 calls)
>> <1139867722<5 GETQUOTA user.scottrus
>>>1139867722>* QUOTA user.scottrus (STORAGE 7 800000)
>> 5 OK Completed
>> <1139867727<6 SETQUOTA user.scottrus ()
>>>1139867727>6 OK Completed
>> <1139867730<7 GETQUOTA user.scottrus
>>>1139867730>* QUOTA user.scottrus ()
>> 7 OK Completed
>
> However the quota command still shows some odd results for user.scottrus
> after attempting to remove the quota:
>
>> bash-3.00$ /usr/lib/cyrus-imapd/quota -f
>> Quota % Used Used Root
>> 600000 0 0 user.drfickle
>> 600000 0 4120 user.lnxgeek
>> 600000 0 0 user.osubeav
>> 7 user.scottrus
>From what I understand everything is okay here. For user.scottrus only the
size of the mailbox is shown, no quota is shown because it is set to -1 in
the quota db. I think the problem is that the quota file (assuming you are
using quota legacy db) is not removed when setting quota to none, instead
the quota is set to -1. quota -f reports for every used who has a quota
file, but correctly shows no quota for it.
What exactly do you consider broken here?
Simon
More information about the Info-cyrus
mailing list