Question

So What ate my disk space?

I have an entry level doplet (20GB) and have some files and an unfinished project. Today I tried to install VCN But the installation stopped halfway because there was not enough space. here is my usage,

root@aaa:/# du -s * | sort -nr | head du: cannot access ‘proc/19923/task/19923/fd/4’: No such file or directory du: cannot access ‘proc/19923/task/19923/fdinfo/4’: No such file or directory du: cannot access ‘proc/19923/fd/4’: No such file or directory du: cannot access ‘proc/19923/fdinfo/4’: No such file or directory 5496816 var 1330076 usr 1048580 swapfile 394848 lib 63980 boot 41200 root 11312 sbin 9328 bin 6688 etc 740 1.sql

And the df is, root@aaa:/# df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 20G 20G 0 100% / none 4.0K 0 4.0K 0% /sys/fs/cgroup udev 239M 4.0K 239M 1% /dev tmpfs 50M 352K 50M 1% /run none 5.0M 0 5.0M 0% /run/lock none 248M 0 248M 0% /run/shm none 100M 0 100M 0% /run/user I want to know where is my disk space. and what is this proc folder? Sorry for bad English.

Subscribe
Share

Have you tried running the command inside the var and usr directories?

As you have 5GB Var and 1.3GB usr folder

You can see you have a 1GB Swapfile

The proc folder contains information about processes and system information. You don’t really need to worry about it.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This question was answered by @snapshooter:

Have you tried running the command inside the var and usr directories?

As you have 5GB Var and 1.3GB usr folder

You can see you have a 1GB Swapfile

The proc folder contains information about processes and system information. You don’t really need to worry about it.

View the original comment

In some cases, it could be coming from Jenkins or Docker (or like that). To solve that, you should clean logs and set it’s size.