How do I find out what is using up all the space on my / partition?

-

In a linux instance. I run the df command and get:

root@db:~# df -h  Filesystem            Size  Used Avail Use% Mounted on  /dev/sda1             9.9G  9.1G  284M  98% /  tmpfs                 3.8G     0  3.8G   0% /lib/init/rw  varrun                3.8G  116K  3.8G   1% /var/run  varlock               3.8G     0  3.8G   0% /var/lock  udev                  3.8G   80K  3.8G   1% /dev  tmpfs                 3.8G     0  3.8G   0% /dev/shm  /dev/sdb              414G  957M  392G   1% /mnt  /dev/sdf               50G   12G   35G  26% /byp  /dev/sdk               99G   31G   63G  33% /backups

I then run the du command and get:

root@db:/# du -s -h /*  31G     /backups  5.5M    /bin  136K    /boot  12G     /byp  80K     /dev  5.8M    /etc  12K     /home  70M     /lib  11M     /lib32  0       /lib64  16K     /lost+found  759M    /mnt  4.0K    /opt  du: cannot access `/proc/6917/task/6917/fd/4': No such file or directory  du: cannot access `/proc/6917/fd/4': No such file or directory  0       /proc  31M     /root  7.7M    /sbin  4.0K    /selinux  4.0K    /srv  0       /sys  11M     /tmp  1.1G    /usr  114M    /var

Solution:


It's entirely possible that you have a very large deleted file (or lots of little ones) that a process still has an open file handle on. The way to find them is to run

# lsof | grep "deleted"

If you see lots of lines that end with "(deleted)" then you can find the process Id that has them open and restart it. Once that happens, your disk space should return.


Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more