4GB limit and possible integer overflow on quotas in v2.2.4
wrobel at kolabsys.com
Thu Aug 19 21:48:38 CEST 2010
Zitat von Gavin McCullagh <gavin.mccullagh at gcd.ie>:
> I have two problems with the cyrus quotas in kolab v2.2.4.
> == Quota Limit ==
> If I modify a user's quota in the web admin interface, the admin interface
> refuses to set a quota higher than 4GB. I get the error:
> Quota must be smaller than 4096
Only fixed in HEAD -> Kolab Server 2.3. You should be able to fix this
manually on your machine.
> == Possible Integer Overflow?? ==
> If I try to set the quota in cyradm, it accepts the higher quota limit, but
> there seems to be something wrong with how cyradm actually reports the
> quota usage.
> localhost> lq user/yyyyyyyyyy at xxxxx.xxxx
> STORAGE 860853/10000000 (8.60853%)
> and similarly, the quota file has:
> gavinmc at xxxxx:~$ sudo cat
> Also, Horde reports a similar usage.
> However, when I look at the disk usage in that directory on the filesystem
> I see:
> gavinmc at xxxxx:~$ sudo du -hs
> 7.9G /kolab/var/imapd/spool/domain/x/xxx.xx/y/user/yyyyyyyyy
> I can see a somewhat similar bug report is resolved here, but there seems
> to still be a problem here. Is this an perhaps an integer overflow bug in
> the code that measures the quota usage?
This is just the 4GB problem (see above)
Could it relate to this one: https://issues.kolab.org/issue2310 ?
> Kolab-users mailing list
> Kolab-users at kolab.org
Developer, Kolab Systems AG
e: wrobel at kolabsys.com
t: +49 700 6245 0000
pgp: 9703 43BE
This message was sent using IMP, the Internet Messaging Program.
More information about the users