Investigate disk use by identifying the full filesystem and the data responsible before deleting anything. Webmin shows system storage, while Virtualmin domain quotas describe a particular account allocation; these measurements can differ legitimately.
IN THIS ARTICLE
Gather the details you will need
Record the affected mount point, free space, inode availability and account quota. Use authorized access and protect customer data. Check whether the incident concerns the operating-system root filesystem, a separate home volume or backup storage.
01 Investigate disk usage through Webmin
- Inspect the dashboard storage summary and System > Disk and Network Filesystems to identify the mounted filesystem behind the affected path. Do not format or unmount a device as a diagnostic step.
- Compare system free space with the relevant Virtualmin account usage and quota. A full host volume can affect users who are below their individual allowance.
- Use a permitted file-manager size view or a scoped administrator disk-usage command to locate growth in logs, mail, application uploads, caches and backup staging. Stay on the intended filesystem when investigating large directory trees.
- Check scheduled backup activity and retention. Preserve verified off-server recovery copies before removing obsolete local archives.
- If deleting known disposable files does not free space, investigate processes holding deleted files open. If writes fail despite free bytes, inspect inode exhaustion, quotas and read-only filesystem state.
- Perform a controlled cleanup approved for the data owner, or plan a supported storage expansion. Then fix the retention or repeated-error condition that caused growth.
Why is my account below quota while uploads fail?
The underlying server filesystem may be full, out of inodes or read-only. Account quota is only one of the limits involved in writing a file.
Confirm the expected result
Confirm free bytes and inodes improve on the exact affected filesystem. Test the previously failing upload, mail delivery or database operation. Recheck after the next scheduled job to ensure the same accumulation does not immediately recur.
If the problem continues
Do not recursively delete unknown files below database or mail storage. Avoid force-unmounting an active service volume. A filesystem reporting errors or becoming read-only requires storage diagnosis and protected recovery, not just quota adjustments.