cPanel disk usage high, but where's all my inode usage going?
hey folks,
i just launched a new SaaS landing page last week, pretty excited about it! but i'm already trying to keep a lid on my hosting costs, you know how it goes.
the thing is, cPanel is reporting really high disk usage, but when i dive in and do some manual checks, the numbers just don't seem to add up. it's especially my inode usage that's through the roof, which is kinda confusing.
i've already gone through the usual suspects:
- cleared out old emails from all accounts.
- checked for any forgotten large backups (none found).
- deleted temporary files i could spot.
i also ran du -sh * in my public_html directory and a few other main directories, and it always shows way less than what cPanel reports as total usage. it's like there's a ghost in the machine.
here's a dummy output from my SSH, just to give you an idea:
4.0K ./.well-known
2.0M ./public_html
8.0K ./mail
12K ./.cpanel
4.0K ./tmp
2.1M total...but cPanel says i'm using like 1.5GB! and my inode usage is at 90%!
so, my specific question is: how can i accurately pinpoint what's *really* eating up my disk space and inode usage in cPanel when all the usual checks just aren't cutting it? are there common hidden culprits like session files, old logs, or server-side caches that aren't visible through regular SSH commands? or maybe some specific server-side logs i should be looking at to recieve better clarity?
thanks in advance for any insights!
2 Answers
Tariq Koffi
Answered 3 days agoHello Chisom Diallo,
it's like there's a ghost in the machine.
I completely get this frustration. It's a classic scenario when you're trying to keep a tight lid on hosting costs, especially after launching something new for SaaS growth. I've been there myself, scratching my head over discrepancies between cPanel and SSH reports. The key difference often lies in what cPanel monitors versus what your `du -sh *` command covers. Your `du -sh *` command likely only scans the current directory and its immediate subdirectories, missing files located outside your immediate home directory (e.g., system-level temp files, certain logs, or even files from other users if you're on a shared host and cPanel is reporting the entire account's usage, including things you don't directly own but are billed for).
To get a more accurate picture of your disk usage, try running du -sh /home/yourcpanelusername/* from the root (or just `~`) of your SSH session. Replace `yourcpanelusername` with your actual cPanel username. This will give you a breakdown of all top-level directories within your account, including those that might not be directly under `public_html`. Common hidden culprits include old session files (often in `/tmp` or a session directory specific to your application), extensive server-side caches (from WordPress plugins, other CMS, or even server-level caching like LiteSpeed or Nginx), and application-specific log files that grow rapidly. For inode usage, which tracks the number of files and directories, the biggest offenders are typically large quantities of very small files. Think about email messages (even if cleared from mailboxes, they can reside in server-side junk/trash folders), WordPress transient files, old plugin cache files, and again, session files. To specifically pinpoint inode hogs, try running find . -xdev -printf '%h\n' | sort | uniq -c | sort -rn | head -10 from your home directory to see which directories contain the most files. This will quickly show you where those tiny files are accumulating.
What kind of caching mechanisms are you currently employing for your SaaS landing page?
Chisom Diallo
Answered 3 days agoAh, this is super helpful, thanks for breaking it all down. That `find` command for the inode usage is exactly what I needed to know, will def give that a try later tonite. Hopefully it uncovers the ghost!