Emergency server help: get in touch

cPanel Quotas Unlimited: fixquotas Repair

Why cPanel accounts show unlimited or zero disk usage after a migration, reboot or filesystem change, and how to repair user quotas on XFS and ext4 with fixquotas, mount options, quotacheck and the XFS project-quota caveats on AlmaLinux 9 and 10.

Published Updated 8 min read

Short answer: When WHM shows every account as unlimited or 0 MB, the kernel is not tracking quotas on the filesystem that holds /home, so cPanel has nothing to read. Run /usr/local/cpanel/scripts/fixquotas. On ext4 that is usually enough. On XFS, quota accounting can only be switched on at mount time, so add uquota to /etc/fstab and unmount and remount /home, or for an XFS root add rootflags=uquota to the kernel command line and reboot. Check the state with quotaon -p /home. (Reviewed October 2026.)

Applies to cPanel & WHM 112 and later (Initial Quota Setup and How to Fix Quotas docs) on ext4 or XFS filesystems; XFS steps follow xfs_quota(8) and apply to AlmaLinux, CloudLinux and other RHEL-compatible systems using grubby

When every account in WHM » List Accounts shows a quota of “unlimited” or disk usage of 0 MB, the accounts have not actually lost their limits. The kernel is no longer enforcing or reporting filesystem quotas on /home, so cPanel has nothing to show. It happens after a fresh install where the mount options were never set, after a migration to a new volume, after a kernel or OS upgrade that changed how XFS handles quotas, and sometimes simply after a reboot on a server where /etc/fstab was edited by hand. The fix is short, but XFS and ext4 need different handling and getting it wrong can mean a reboot.

Confirm what the kernel is doing

Start by checking whether quotas are active at all on the filesystem holding /home:

findmnt -no SOURCE,FSTYPE,OPTIONS /home
quotaon -p /home
repquota -a | head

If /home is not a separate mount, run the same commands against /. quotaon -p reports whether user quotas are on or off. If it says off, or if repquota returns nothing, the kernel is not tracking usage. Also confirm cPanel agrees:

whmapi1 accountsummary user=USERNAME | grep -E 'disklimit|diskused'

Run fixquotas first

cPanel’s own repair script handles the common cases: it adds the right mount options, remounts, runs quotacheck where the filesystem type requires it, and turns quotas on:

/scripts/fixquotas

Watch the output. On ext4 it runs quotacheck -avugm, which walks the whole filesystem and can take a while on a large volume with heavy I/O; do it out of hours. On XFS it usually reports that quotas need a mount option and a remount, which is where the XFS caveat below applies. When it finishes, re-run repquota -a and reload List Accounts. If the numbers are back, you are done apart from verifying the mount is persistent.

ext4: mount options and quotacheck

On ext4, quotas are enabled through mount options and stored in aquota.user at the root of the filesystem. The /etc/fstab entry needs usrquota (and grpquota if you use group quotas, which cPanel does not by default):

UUID=...  /home  ext4  defaults,usrquota  0 2

Then apply without a reboot:

mount -o remount /home
quotacheck -cugm /home
quotaon -v /home

Modern ext4 also supports journaled quotas set at tune2fs level (tune2fs -O quota /dev/sdX), which do not need the aquota files or quotacheck. cPanel works with either. A common pitfall on ext4 is a stale aquota.user from a previous filesystem copied over during a migration with rsync; delete it and re-run quotacheck.

XFS: the option must be set at mount time

XFS is the default on AlmaLinux 8, 9 and 10 and it treats quotas differently. The uquota (or usrquota) option cannot be applied by remount; the filesystem must be unmounted and mounted again with the option, or the server rebooted. That is fine for a separate /home, but for a root filesystem it means a reboot, and for an XFS root you also have to pass the option on the kernel command line:

grubby --update-kernel=ALL --args="rootflags=uquota"

For a separate /home on XFS, the fstab line is:

UUID=...  /home  xfs  defaults,uquota  0 0

Then, out of hours, stop the services that hold files open in /home and remount:

systemctl stop httpd cpanel exim dovecot mariadb
umount /home
mount /home
quotaon -p /home
systemctl start mariadb dovecot exim cpanel httpd

If umount fails with “target is busy”, lsof +D /home | head shows what is still open; usually a PHP-FPM pool or a stuck backup. XFS tracks usage in its metadata, so no quotacheck is needed and quotas are accurate as soon as the mount comes up. If the option was already in fstab but quotas are still off, the mount happened before the option was added, and an unmount and mount (or a reboot, for an XFS root) is all that is missing; mount -o remount does not switch on XFS quota accounting.

Check dmesg | grep -i quota after the mount for any complaint from the kernel.

cPanel-side data drift

Occasionally the kernel is fine but cPanel’s cached usage is wrong: an account shows 0 MB while repquota shows gigabytes. cPanel reads the values through quota calls but also caches them for the interface. Refresh both:

/scripts/fixquotas
/usr/local/cpanel/scripts/update_db_cache
/scripts/updateuserdomains

Also make sure the quota is actually set on the account, not just on the package: whmapi1 editquota user=USERNAME quota=10240 sets a 10 GB limit, and quota=0 is unlimited. Accounts created while quotas were off may have been created with an implicit 0.

Mail and database usage

Two figures in cPanel are not filesystem quotas and confuse the picture. Mailbox quotas are Dovecot’s own, held in /home/USER/etc/DOMAIN/quota, and show correctly even when filesystem quotas are broken. Database usage is included in an account’s total only if WHM » Tweak Settings » Include databases in disk usage calculations is on, and it comes from MariaDB (through INFORMATION_SCHEMA by default, or from the data directory if that Tweak Setting is off), not /home. If a customer’s total does not match du -sh /home/USER, check that setting before assuming quotas are wrong.

Verify

After the fix, all of these should agree for a test account:

quota -u USERNAME
repquota /home | grep USERNAME
whmapi1 accountsummary user=USERNAME | grep -E 'disklimit|diskused'

Create a large file as that user to confirm enforcement, and expect a “Disk quota exceeded” error at the limit. Use a test account with a small quota and make sure /home has more than 20 GB free first, because if quotas are still not enforced dd writes the whole 20,000 MB file:

su -s /bin/bash USERNAME -c 'dd if=/dev/zero of=~/quotatest bs=1M count=20000'
rm -f /home/USERNAME/quotatest

Finally, reboot at a maintenance window once and re-check quotaon -p /home afterwards. A quota setup that survives a reboot is the only one that counts, and fixquotas is worth a place in your post-migration checklist alongside the steps in migrating cPanel accounts to a new server.

cPanel quotas unlimited at a glance

cPanel Quotas Unlimited – short answer
In short: Why cPanel accounts show unlimited or zero disk usage after a migration, reboot or filesystem change, and how to repair user quotas on XFS and ext4 with fixquotas, mount options, quotacheck and the XFS project-quota caveats on AlmaLinux 9 and 10.
cPanel Quotas Unlimited – what this guide covers
cPanel Quotas Unlimited: what this guide covers.
cPanel Quotas Unlimited – questions answered
cPanel Quotas Unlimited: the questions this guide answers.

Official documentation (checked 9 October 2026): cPanel docs: How to Fix Quotas · cPanel docs: Initial Quota Setup · xfs_quota(8) · xfs(5) · quotaon(8) · quotacheck(8) · tune2fs(8) · WHM API 1: editquota · cPanel docs: Tweak Settings – SQL · cPanel Support: Database count and disk usage stats are not updating · findmnt(8)

Related guides: Replacing cxs: malware scanning with LMD (maldet), ClamAV and ImunifyAV on hosting servers · “cPanel license is invalid”: troubleshooting manage2, IP changes and firewalls · Incident response after a cPanel root-escalation CVE: rotating keys, hunting .sorry, auditing sessions.

Undo or roll back

  • Before editing, copy the mount table with cp -a /etc/fstab /etc/fstab.bak and check every edit with findmnt --verify before you remount or reboot; a typo in /etc/fstab can stop the server booting.
  • To revert the mount options, restore the copy (cp -a /etc/fstab.bak /etc/fstab), run quotaoff -v /home, then remount on ext4 or unmount and mount again on XFS.
  • To remove the XFS root option from the kernel command line, run grubby --update-kernel=ALL --remove-args="rootflags=uquota" and reboot.
  • Record an account’s current limit with whmapi1 accountsummary user=USERNAME before changing it, and put it back with whmapi1 editquota user=USERNAME quota=OLDVALUE (value in MB; 0 or unlimited means no limit).
  • If you deleted a stale aquota.user on ext4, quotacheck -cugm /home recreates it from the current files.

Frequently asked questions

Does fixquotas work on XFS without a reboot?

Only if /home is a separate XFS filesystem that you can unmount and remount with the uquota option; an XFS root filesystem needs rootflags=uquota on the kernel command line and a reboot.

How long does quotacheck take on a large ext4 /home?

It scans every inode on the filesystem, so a multi-terabyte volume with millions of files can take from tens of minutes to a few hours under load; run it out of hours, or use journaled quotas via tune2fs to avoid it.

Can I run fixquotas while customer sites are live?

On ext4, yes, though quotacheck adds I/O; on XFS the unmount step requires stopping Apache, Exim, Dovecot, MariaDB and cPanel briefly, so schedule it as a maintenance window.

Maintenance record

This guide changes servers, data or security settings, so we re-check it against current versions on a fixed schedule. Take a backup or snapshot before you start.

Maintained by
srvScripts editorial team
Supported versions
cPanel & WHM 112 and later (Initial Quota Setup and How to Fix Quotas docs) on ext4 or XFS filesystems; XFS steps follow xfs_quota(8) and apply to AlmaLinux, CloudLinux and other RHEL-compatible systems using grubby
Last full review
Next review

Share this guide

Free website test

Is your website set up right?

Check SSL, security headers, redirects, robots.txt, sitemap, llms.txt and security.txt in one test. It takes about 30 seconds.