Portal Home > Knowledgebase > Articles Database > DF Shows zero avalable space
DF Shows zero avalable space
| Posted by ballighohosting, 08-04-2015, 05:31 AM |
| Hi,
df -h shows zero available space although I freed up over 600 GBs of data:
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 1.8T 1.8T 0 100% /
tmpfs 16G 0 16G 0% /dev/shm
/dev/sda2 504M 58M 422M 12% /boot
the system is running on solusvm control panel with openvz support ..
please help..
Thanks..
|
| Posted by prologan, 08-04-2015, 07:12 AM |
| lsof -nP | grep '(deleted)'
http://unix.stackexchange.com/questi...e-been-deleted
|
| Posted by Syslint, 08-04-2015, 07:14 AM |
| What is the result of the following command
# df -iH
|
| Posted by PlatinumVPS, 08-06-2015, 04:25 AM |
| Are you seeing the same resources at SolusVM control panel? Did you reboot your system after removing the data? If not then reboot your machine once and again check the usage.
|
| Posted by artemirk, 08-06-2015, 05:21 AM |
| You need find already deleted, but still opening files. It's didn't clean from disk.
lsof -nP | grep '(deleted)'
Looking for files you already deleted, or some log files.
At 1st column you will see process which still open file. Just restart.
Also you can culculate current file size:
du -hs /
-h - human size G M
s - show summary for /
Size for each dir:
du -hs /*
If size is ok just reboot, if you can.
If not:
You need find already deleted, but still opening files. It's didn't clean from disk.
lsof -nP | grep '(deleted)'
Looking for files you already deleted, or some log files.
At 1st column you will see process which still open file. Just restart.
|
| Posted by CharlsJoseph, 08-06-2015, 05:46 AM |
| Hello,
If you already freed up data then just check after restart.
|
| Posted by Johnny Cache, 08-06-2015, 05:46 AM |
| This is exactly what happens when you don't partition /vz separately from the file system... not the most fun thing in the world to deal with.Are you running quite a few containers under the Ploop format (http://openvz.org/Ploop) ...? I think it's default in SolusVM now-
You may just need to shrink some of those down.(look for instances of "/dev/ploopXXXXX" in /proc/mounts on the node. Note the associated container ID ($CTID).
# vzctl compact $CTID
If you have any OpenVZ Ploop containers, this "online shrinking" as OVZ calls it, will almost certainly free up a hefty chunk of that disk space.If not... you'll have to free up enough space even to migrate any of these to another machine.,, no room to store the dump file ... for your sake I hope the fs trim works for you.
|
Add to Favourites 
Print this Article
Also Read
