• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Quota's not enforced

M

madcat

Guest
Hello. When running 'repquota -va' from the Bash command line as root, I am seeing that the vast majority of users have a '0' for both their soft and hard quotas, although some users setup via the Plesk control panel have proper values for the hard quota. Any ideas why this is, and how to go about making it so that the quota setup for a user in Plesk is setup as a filesystem hard quota?

Thanks.
 
Hello,

Actually, you are right, quota setup for system users in Plesk should match to the same users on the server.
Could you please specify where exactly have you checked this value?

"Hard disk quota" in Plesk is a file system feature and it limits how much disk space can be taken by files which are owned by a specific system account (either domain FTP user or webuser or subdomain FTP user). This file system quota cannot be exceeded and if the limit is reached, the system user will not be able to create files anymore but error "no more space left on device" will appear. You can set domain hard disk quota on the domain hosting setup page Domains -> DOMAIN_NAME -> Setup -> Hard disk quota.
 
In "Domains -> DOMAIN_NAME -> Setup -> Hard disk quota" the Hard disk quota is set to Unlimited. However, in "Domains -> DOMAIN_NAME -> Limits" a limit is setup, as well as in "Clients -> DOMAIN_NAME -> Limits". I am begining to think Plesk has too many different ways to set the disk space limit. It appears there is no limit unless it is set in the "Setup" icon. The other types of limits just change the control panel icon and send an email out, which we don't have time to deal with and the customer just ignores as they happily use up more disk space than they are paying for.

Plesk should fix this *bug* so that a hard quota is setup for every potential disk space user, including FTP uploaders, MySQL users, and, in most importantly, mail box users. The bigest problem is that there are tonnes of email accounts that are not being monitored, but are filling up with SPAM.

Thanks for your reply, Satoriya.
 
Back
Top