Today I ran across a problem and I’m not sure if it’s a wrong configuration of my hosting provider, because I haven’t changed anything about the file system.
df -h says:
df -h Filesystem Size Used Avail Use% Mounted on /dev/simfs 50G 2.4G 0 100% /
It says it’s 100% used, but only 2.4G of 50 are really in use. I’ve also tried to delete some logfiles which were big, but it didn’t help.
I’ve also checked with “du -sh *” if there’s anything big, but couldn’t find anything large.
Anyone has an idea?
There are enough INodes free.
df -hi Filesystem Inodes IUsed IFree IUse% Mounted on /dev/simfs 25M 137K 25M 1% /
df -T Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/simfs simfs 52428800 2127284 0 100% / none devtmpfs 262144 4 262140 1% /dev none tmpfs 52432 56 52376 1% /run none tmpfs 5120 0 5120 0% /run/lock overflow tmpfs 1024 0 1024 0% /tmp none tmpfs 209700 0 209700 0% /run/shm none tmpfs 102400 0 102400 0% /run/user
ls -la /dev/simfs brw------- 1 root root 144, 149 Aug 14 00:01 /dev/simfs
You’re using an OpenVZ-based VPS, and on this VPS your root filesystem isn’t really a filesystem, but a directory on the host. That directory on the host has run out of disk space.
This is a strong sign that your provider has significantly overcommitted resources and isn’t monitoring them well, or at all. The replacement for simfs, known as ploop, is more difficult to overcommit, has a stronger guarantee of disk space, and performs better.
I would strongly advise you to find another provider as soon as possible. This is very unlikely to be the last problem you will have with your current one. (And, of course, one not based on OpenVZ.)
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.