dovecot - Nov 2014 - Understanding filesystem quotas

Hello:

I've been trying to set up filesystem quotas for IMAP, and cannot seem to
get it to work.  In IMAP clients it either shows quota unavailable or
unknown.  I've read the documentation several times.

I've enabled the quota plugins and to my knowledge that part is good.
I've edited the file 90-quota.conf and uncommented these lines and set them
as follows:

plugin {
quota_rule = *:storage=1G
}

plugin {
quota = fs:User quota:user
}

To my knowledge, this should enable filesystem quotas by user.  However when
I run "doveadm quota get -u username", it shows:

Quota name Type    Value Limit                             %
User quota STORAGE     0     -                             0

So basically all zeros.  I've also tried running "doveadm -Dv quota get
-u
username" and don't see anything that stands out or that would indicate
an
issue.  It shows the correct block device and such.  I know filesystem
quotas are working as I can run "quota username" and it shows the
usage.

The reason I picked filesystem quotas is because we have
/var/spool/mail/username (spool file), and /home/username/mail on the same
partition, and because it sounds like it's fast and doesn't require disk
I/O.  But I'm trying to also figure out by setting the "storage="
command in
Dovecot, do I even need to set a hard and soft limit on the filesystem quota
then? I would prefer to let Dovecot enforce quotas rather than rely on the
filesystem quota mechanism, but keep disk I/O down.

Any help would be greatly appreciated on this.  Thank you.

--
Chris

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 13 Nov 2014, Chris Szilagyi wrote:
> I've enabled the quota plugins and to my knowledge that part is good.
> I've edited the file 90-quota.conf and uncommented these lines and set
them
> as follows:
>
> plugin {
> quota_rule = *:storage=1G
> }
>
> plugin {
> quota = fs:User quota:user
> }
>
> To my knowledge, this should enable filesystem quotas by user.  However
when
> I run "doveadm quota get -u username", it shows:
>
> Quota name Type    Value Limit                             %
> User quota STORAGE     0     -                             0
>
> So basically all zeros.  I've also tried running "doveadm -Dv
quota get -u
> username" and don't see anything that stands out or that would
indicate an
> issue.  It shows the correct block device and such.  I know filesystem
> quotas are working as I can run "quota username" and it shows the
usage.
Are you sure, that you:

1) have enabled quotas on /home/username/mail,
2) have reloaded Dovecot after config change,
3) have read dovecot logs, if there are errors, and
4) maybe you need to configure a limit, in order to enable quotas in 
Dovecot at all.
5) maybe try the mount=<path> option, http://wiki2.dovecot.org/Quota/FS
> then? I would prefer to let Dovecot enforce quotas rather than rely on the
> filesystem quota mechanism, but keep disk I/O down.
Dunno if "rely" sounds like you don't trust it ;-) But you should
place
INDEXes somewhere else, if you enforce quota via file system.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEVAwUBVGWv+nz1H7kL/d9rAQItSAf/X0kPLMAFkr0u6FxN7UqVpV2HB7OGLGUE
kD4d9Q8a26lR4xxOy1QpTyOC6NzVO+uX+Hutsn4inZN61EIBy0r/Y2b0sS9YNbir
XG76V0mTB8+zfY0Av7nX3jCYNaxnfiZeqltd4D7u+es71QXvLyCbYfIVB/ZuzsTj
P/KxurHflvbDeqVT89hFZnRpUQdFZXLFQeMAjAtBl9uvmtrItemlY7rsXhoqNPg8
0tEvvjYKt1diNGDRqczstB3wCUb7ixkhPvy3O8Mff8HzMW5n9sVbjTu4NIsAjWRS
lNejGaPQtMLZutvOLxVuMz5Xa6U4Ct14iStlncwg6YQiL9sOGcDKYA==isFV
-----END PGP SIGNATURE-----