Global Disk Quota Limit for cPanel/WHM Servers
Dear cPanel Team,
I would like to submit a feature request that I believe would be very valuable for system administrators and hosting providers using cPanel/WHM.
đź“Ś Feature Requested:
Ability to define a global disk usage quota limit across all cPanel accounts on a server.
🎯 Purpose:
To prevent the entire server from becoming unresponsive or going offline due to one or more cPanel accounts consuming excessive disk space in an unmonitored way — especially on systems where the total available space is limited.
🔍 Use Case:
In current implementations, each account can be limited individually via packages or manual settings, but there is no built-in mechanism to stop the server from exceeding a total safe disk threshold (e.g., 95% of /home, or 100 GB cumulative space).
If one account grows unexpectedly large — due to logs, emails, backups, or abuse — it can consume most or all of the available disk space. This can lead to:
-
Server instability or crashes
-
Inaccessible WHM and cPanel interfaces
-
All hosted websites going offline
-
Failed backups, email queues, or database corruption
âś… Suggested Implementation:
-
A global disk quota setting at the WHM level (e.g., “Maximum total disk usage across all accounts: 100 GB”)
-
Hey there! This isn't a tool we're looking to add at this time. There is a notification system that can alert you when the server's disk usage reaches a certain threshold, and you can find details on that here:
https://support.cpanel.net/hc/en-us/articles/11670187451799-How-to-configure-disk-usage-alerts
so that would at least alert the server administrator before things reached a critical level.
0 -
What happens if that global disk quota is reached?
Doesn't it mean that all cPanel accounts are over quota?
0 -
cPRex I understand your response. It has happened to me more than once to have errors that generated tens of gigabytes of logs in a very short time, leaving me no choice and ending up blocking my server and the block no longer allowed me to access the WHM interface.
0 -
Could you share specifically where those log files were located on the system?
0 -
These were logs related to a Magento and Redis installation.
0 -
cPRex The issue, beyond the potential file corruption, is precisely the lack of access to WHM, which always forces me to contact the hosting support or the server administrator — and that can be really frustrating at times.
0 -
Would lack of access to WHM help fix a file system issue, though? Normally if the logs are in a root-owned directory they would need to be removed from the command line:
0
Please sign in to leave a comment.
Comments
7 comments