Use the authorized account or server administrator as appropriate. Record the username, reported quota, current usage and time. Identify the filesystem containing its data and whether the concern is a user quota, full filesystem or inaccurate panel tally.

1. Compare the panel account usage with its breakdown for website, mail, databases and backups. Note whether a scheduled backup was running during the last tally.
2. At server level inspect filesystem capacity and inode availability, then inspect the relevant user quota using the tool appropriate to the filesystem. Do not apply ext-family quota commands blindly to XFS.
3. Look for large account-owned files outside the obvious document root, accumulated mail and local backup staging. Inspect ownership rather than assuming every byte below a shared service directory belongs to the same user.
4. If filesystem accounting is correct but the panel figure is stale, use the documented scoped tally workflow for the affected user. Avoid repeatedly scheduling an all-user tally on an already overloaded server.
5. If real usage exceeds the allowance, agree a retention cleanup or suitable plan change. Preserve needed data and verify remote backup copies before removing local archives.

At an authorized Linux shell, replace /home/USERNAME with an existing path inside the affected account. These commands report the filesystem containing that path:

df -h /home/USERNAME
df -i /home/USERNAME

The first reports filesystem space; the second reports inode use. A filesystem can have free bytes while running out of inodes, and both can have capacity while an individual account has reached its quota. Neither command measures the account quota or reproduces DirectAdmin's website, mail and database tally.

Compare the result with the account quota and the panel breakdown captured at the same time. If the filesystem is full, use the linked capacity-recovery guide; if only the panel total is stale, follow the scoped tally procedure. Do not delete customer files simply to make these different measurements match.

Yes. A tally during archive creation can count temporary account-owned backup data. Confirm the job has finished and inspect the next accurate tally before concluding that customer files have duplicated.

After the relevant accounting process finishes, compare the same measurements again. Confirm uploads or mail delivery now work and that usage remains sensible after the next scheduled tally. Record which component explained the difference.

If a filesystem is actually full, handle it as a server-capacity incident. Deleted files still held open, inode exhaustion and filesystem quotas need different remedies. Do not disable quotas globally or recursively change ownership just to make the panel number match.

• Scheduling off-server DirectAdmin account backups
• Recovering service when a Linux filesystem is full
• Finding deleted files that still consume disk space
• Investigating a DirectAdmin brute-force block

• DirectAdmin: Filesystems And Quotas
• DirectAdmin: Disk Usage Bandwidth
• DirectAdmin: Backup Times