• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Calculation of hardquota in service plan

Martin.B

Plesk Certified Professional
Plesk Certified Professional
Hi,

according to the official Administrator's Guide (Appendix A: Ressources), the 'disk space' value in a service plan definition "includes disk space occupied by all files related to the subscription: content of websites, databases, applications, mailboxes, log files, and backup files."

Additionally it's possible to set a hard quota (in supported) in 'hosting parameters'. According to the Guide (Appendix A: Hosting Parameters) "Hard disk quota will not allow writing more files to the web space when the limit is reached"

There is an obvious difference in the wording. While the first explicitly states, that all files are included into the calculation, the definition for the hard quota only speaks about the 'web space', which would be, as I understand it, only the contents of /var/www/vhosts/<domain>/httpdocs.
Since mails and databases are saved as other users (popuser/mysql) this also makes sense, however I'd like to confirm it.
Is anybody using hardquota and can tell, which files are used for the calculation?
 
To answer directly: only files owned by the system user that the quota is set for are taken into account.

Plesk's hard disk quota uses linux system of disk quotas that is dependent on the file ownership. Consequently, files that aren't owned by the system user that the quota is set for, such as email messages or databases, can't be taken into account.

The actual location of the files is not important, just their ownership. E.g. if there are user owned files in /var/www/vhosts/<domain>/httpdocs and the admin copies them to /root/backup/<domain>/httpdocs without changing the file ownership, cumulative size of both copies will be taken into account for the user's hard disk quota.

OS tools can be used to see the quotas after they were set by Plesk:
Code:
quota --user --human-readable --verbose <SYSTEM_USER>
repquota --all --human-readable --verbose
 
Back
Top