Disk Usage
Disk Usage answers the eternal hosting question, "what is eating the disk?", scoped to what each role is allowed to know: totals and percentage up top, per-user consumption with over-quota flags for administrators, a directory breakdown, and the largest files on disk.
Files → Disk Usagehttps://YOUR-SERVER-IP:8443/files/disk-usageWhat each role sees
ROOT sees the whole server: real filesystem totals, every user's consumption with a top-10 chart and over-quota warnings, all home directories and the largest files under /home. ADMIN gets the same server totals, directories and largest files, while the per-user consumption section covers the users in their own chain. RESELLER sees itself plus its own customers, with the reseller's plan quota as the ceiling. USER sees exactly their own usage against their plan quota, and their own domain directories: no neighbors, no server totals.
An inode card appears when the server tracks inode counts, showing file-count usage against the account's inode quota with a warning as it approaches the limit, because "disk full" on shared hosting is as often about millions of tiny files as about gigabytes.
du where it does not) and syncs the results into the panel database. The largest-files list runs a real find over the allowed scope (files above a configurable threshold, 10 MB by default) with its results cached for fifteen minutes, and the user hierarchy view caches for six hours with a force-refresh button when you want the truth right now.Reading the page
The directory table and chart break consumption down per home or domain directory with owner and size; the largest-files table lists path, owner, type, size and modification date, which is usually where the forgotten 8 GB backup archive announces itself. The page is deliberately read-only: cleaning up happens in the File Manager, armed with the paths this page hands you.
Access
Available to every role with the scope rules above (see roles and permissions), enforced server-side per endpoint. Administrator sections (user consumption, hierarchy) are simply absent from a user's view rather than locked.