Hi,

for starters: I'm not a complete *nix noob but by far no pro either

I got a CentOS / Virtualmin server where my root-partition is currently at 98% but I can't seem to find what's eating up my disk space
Below is the output of the df-command, attached is a screenshot of the output of du "-hsx * | sort -rh | head -25", clearly showing only 27 GB of space is used (and most of it in the home-directory which is a seperate partition! (see screenshot here: https://imagebin.ca/v/3GlMwlomsqhi )



[ /]$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/centos_xyz_-root 52403200 51305828 1097372 98% /
devtmpfs 3994544 0 3994544 0% /dev
tmpfs 4005208 0 4005208 0% /dev/shm
tmpfs 4005208 107052 3898156 3% /run
tmpfs 4005208 0 4005208 0% /sys/fs/cgroup
/dev/vda1 508588 223260 285328 44% /boot
/dev/mapper/centos_xyz_home 257511644 17981888 239529756 7% /home
tmpfs 801044 0 801044 0% /run/user/0
tmpfs 801044 0 801044 0% /run/user/1000

As for as I know, du by default doesn't display hidden files/folder, although they are counted for. So I suggest you use this command instead to see sizes of hidden files/folders as well.

You can repeat this same command in each directory/partition to have a clear idea as to what is eating your space.

find / -xdev -size +99M -ls
Or maybe -mtime Or other find switches...
Web-search: linux find what is filling up disk
http://www.linuxquestions.org/questi...t-it-is-758699

If you are NOT in a hurry.

$ du -h --max-depth=1 /

Then du down the rabbit hole for anything HUGE and track down where your space went. If /dev/ shows up as HUGE, you might have replaced /dev/null with an actual file (I did that once). Otherwise most of /usr/share/doc/ can be trimmed down in a crunch. And various /var/ places depending on package archives and bloated log files. But most times one too many media files in $HOME is what hogs my space.

Two possibilities:

1. When you run "du -hsx *", your shell expands the "*" and does not include files with names that begin with ".". It's not terribly likely that you have huge dotfiles in the root directory, but you can include those by running "du -hsx /". I suggest using the "--max-depth=1" option to reduce the clutter.
2. You could have files hidden under an active mount point. You can examine the root filesystem as it would appear without the mounts by running
   Code:

   mkdir /tmp/tmproot
   mount --bind / /tmp/tmproot
   du -hsx --max=depth=1 /tmp/tmproot

   If there are files where you don't want them, you can move or delete them from /tmp/tmproot. Run "umount /tmp/tmproot" and delete that directory when you are done.

Also note that open files consume disk space, even if there is no directory-entry (yet) pointing to them. And, if there is one, the directory entry probably is not up-to-date with the actual file size at the immediate instant.

is your friend

Thanks all for your feedback (most things I found & tried myself). This one was the trick.... I deleted a whole lot of log & temp files... so they didn't show up in the filesize ... but did still consume disk space. One reboot and I've got plenty of disk space again