Symptoms of a full disk (and the fix)

A full disk on shared hosting shows up as broken uploads, WordPress sites that suddenly can't save changes, emails that bounce, and MySQL errors on pages that worked fine yesterday. Check your plan usage in the portal under Services → your hosting, or in cPanel under Disk Usage. If you're near or at your plan's limit, the fix is almost always the same: find what's eating space, delete or archive it, then clear out the usual junk that piles up without anyone noticing.

The symptoms, in order of how they usually show up

Disk problems rarely announce themselves. They show up sideways:

• Uploads fail silently or with a vague error. Media library uploads in WordPress stall or throw a "unable to create directory" or "disk quota exceeded" message. FTP and File Manager uploads behave the same way.
• Database writes fail. MySQL needs free disk space to write to its own files, so a full disk can cause "table is full" or generic database connection errors, even though the database itself isn't corrupted.
• Email stops working. Mailboxes have their own storage inside your account's disk allocation. When they fill up, incoming mail bounces with a "mailbox full" or "over quota" message back to the sender, and Roundcube may refuse to load.
• Backups may be affected. Backups need working space on disk. If you're consistently full, that's worth ruling out along with everything else.
• Site pages error out inconsistently. PHP needs to write temp files and session data to disk. A full disk can cause random 500 errors that look unrelated to disk space at all.

Find out what's actually full

Start with Disk Usage in cPanel (Meridian theme: check the Dashboard's Disk Usage tile, or the Files section). It breaks usage down by directory, so you can see whether the weight is in public_html, mail, or somewhere else like old backup archives sitting in your home directory.

If you have SSH access, you can get a faster, more precise answer from the command line:

du -sh ~/* | sort -rh | head -20

This lists your top 20 largest items in your home directory, sorted largest first. Run it again inside a heavy folder (like public_html or mail) to drill down further:

du -sh ~/public_html/* | sort -rh | head -20

The usual culprits

Mail that was never cleaned out

Mailboxes with years of accumulated mail, especially ones with large attachments, are a common source of runaway disk usage. Check individual mailbox sizes under Email Accounts. The Spam folder and Trash often hold more than the inbox does, since most mail clients don't empty them automatically.

Old backups and export files

Full-site backups, database dumps, and migration exports (.zip, .tar.gz, .sql files) generated for a one-time task and forgotten are one of the biggest single-file offenders. These are safe to delete once you've confirmed the task they were for is done, since your account's regular backups are handled separately.

Logs that grew unbounded

Custom application logs, PHP error logs, or debug logs left in verbose mode can grow for months without anyone noticing. WordPress's own debug log (wp-content/debug.log) is a frequent one if debug logging was left on. If you're not actively debugging something, turn logging off and delete the file.

Caching and temp directories

Plugin cache folders, old theme/plugin versions left behind after updates, and abandoned staging copies of a site all add up. If you use the LiteSpeed Cache plugin, its cache data is regenerated automatically and safe to clear if it's grown large.

Media libraries with originals nobody resized

Full-resolution photos uploaded straight from a phone or camera, multiplied by however many thumbnail sizes WordPress generates per image, is a slow but steady drain. This isn't something to fix in the moment, but worth revisiting once the immediate issue is resolved.

Clearing space

1. Delete or download-then-delete old backup and export files from your home directory.
2. Empty large mailboxes' Trash and Spam folders, and ask anyone with an old mailbox to archive locally instead of leaving everything on the server.
3. Remove debug and application logs you don't need, and turn off verbose logging if it was left on by mistake.
4. Delete unused WordPress themes, plugins, and any staging or backup copies of the site sitting in a subfolder.
5. Recheck Disk Usage after each step.

If you're consistently near the limit

If cleanup buys you a few weeks before you're full again, that's a sign of ongoing growth, not a one-time mess. Check whether it's mail volume, a media-heavy site, or backup exports being generated regularly, and address the source rather than repeating the cleanup. If the site has genuinely outgrown its current plan, Service actions → Upgrade plan in the portal moves you up, billed prorated.

When to contact support

If du -sh and cPanel's Disk Usage report very different totals, or usage is climbing and you can't find where, open a ticket from Support in the portal. It's a real person, not a bot, and they can look at the account directly rather than you guessing at directories.