Your site was fine yesterday. Today visitors see a suspension page because the account hit 100% disk. Nobody got a warning they understood. The backup plugin has been writing 40 GB of local zip files into wp-content for six months.
Hosts suspend at quota for good reason: full disks corrupt databases and take neighbors down on shared nodes. You still want notice before the cliff. Monitoring disk space is boring until it saves a Friday.
Why disks fill up on "small" sites
- Backup plugins storing every nightly dump on the account (never offloaded to S3 or removed)
- Uploads folder growth (PDFs, hi-res images, WooCommerce exports)
- Log files (error_log, access logs, debug logs left on in production)
- Email mailboxes on the same hosting account eating quota
- Staging copies forgotten in a subdomain directory
- Database bloat (revisions, sessions, Action Scheduler) making dumps huge even if file count looks fine
Read database size creep and shared hosting limits for related traps.
What hosts actually do at 100%
Policies vary: email warnings at 80–90%, write lock at 98%, full suspension until you delete or upgrade. Some hosts stop MySQL writes first. Others replace the site with a generic over-quota page without emailing the billing contact.
Know your provider's thresholds in writing. Add the alerts email to a distribution list someone reads.
Monitor before the panel turns red
cPanel / hosting dashboard: check Disk Usage monthly minimum; drill into which folder grew.
SSH (VPS): df -h and du -sh /* on the account root (carefully).
External uptime monitors: some can warn on disk via agent or API if your host exposes metrics.
Backup plugin settings: cap local retention, push off-server, exclude cache folders.
Cron email reports: weekly script that emails current usage (many agencies script this on client accounts).
Practical cleanup order
- Delete old backup zips in wp-content, home directory, and
backup*folders - Truncate or rotate giant error logs (fix the error after copying a sample)
- Purge cache plugin files and opcode cache temp if safe
- Remove unused staging trees
- Compress or offload old media; empty trash in WordPress
- Clean database tables via reputable plugins after backup
Do not delete random folders because du said they are big. Identify first.
Inodes matter too
Some suspensions are inode limits (millions of tiny files) not gigabytes. Cache plugins, extracted backups, and session files can trigger inode caps while disk % looks fine. Host panels often show inode usage separately. Ask support if the error mentions inodes.
VPS vs shared
Shared: hard quota is real; neighbors do not care about your backups.
VPS: you chose disk size at provision time; growth is your monitoring problem until the volume is full and the OS misbehaves. Snapshots do not free space on the live disk.
Canadian hosting note
Disk in Montreal or Edmonton still fills the same way. Compliance does not shrink log files. If you promise clients data stays in Canada, include backup retention in that story (local zips count as stored data).
Bottom line
Watch disk and inodes before the host suspends you. Automate reminders, fix backup plugins that hoard zips, and treat 80% usage as a ticket to investigate, not a problem for next quarter.
Over quota on Canadian hosting and need cleanup or a plan upgrade? Talk with Swift Host. We will find the folder that ate your account before you guess.
