Disk Usage and Cache Memory
Disk usage at 96G with only a few accounts, and no more than 10 domains. Also, memory usage is high!
Which is most likely from setting up litespeed with memory cache, but how do I clean my system after uninstalling? As this was just a trial run.
Specs
Filesystem Size Used Avail
/dev/sda2 100G 96G 4.7G
/dev/sda1 200M 9.8M 191M
/dev/loop0 3.5G 131M 3.2G
total used free shared buff/cache available
Mem: 7492316 1734684 267612 75272 5490020 5151180
Swap: 1048572 0 1048572
Total: 8540888 1734684 1316184
-
For the disk usage you'd have to look and see what is consuming the disk space. Typically to do this I suggest the following: cd / du -h --max-depth=1
This isn't recursive though and will just show you the usage for the current directory. This will give you an idea where to go to look. cd to the next directory and run it again to see the disk usage allocation. As far as the memory usage, it doesn't look high at all, memory usage in Linux can be confusing, the following article is really helpful in breaking it down Help! Linux ate my RAM!0 -
193M ./boot 7.1M ./dev du: cannot access "./proc/169311/task/169311/fd/4": No such file or directory du: cannot access "./proc/169311/task/169311/fdinfo/4": No such file or directory du: cannot access "./proc/169311/fd/3": No such file or directory du: cannot access "./proc/169311/fdinfo/3": No such file or directory 0 ./proc 34M ./run 0 ./sys 67M ./etc 109M ./root 3.9G ./var 124M ./tmp0 -
That can't possibly be all of the output, it can take some time to complete but the bigger partitions aren't even included here. 0 -
I'm running again 0 -
[root@pharr ~]# cd / [root@pharr /]# [root@pharr /]# du -h --max-depth=1 193M ./boot 7.2M ./dev du: cannot access "./proc/645214/task/645214/fd/4": No such file or directory du: cannot access "./proc/645214/task/645214/fdinfo/4": No such file or directory du: cannot access "./proc/645214/fd/3": No such file or directory du: cannot access "./proc/645214/fdinfo/3": No such file or directory 0 ./proc 213M ./run 0 ./sys 72M ./etc 108M ./root 2.3G ./var 124M ./tmp du: cannot read directory "./usr/share/cagefs-skeleton/proc/sys/fs/binfmt_misc": Too many levels of symbolic links du: cannot access "./usr/share/cagefs-skeleton/proc/645214/task/645214/fd/4": No such file or directory du: cannot access "./usr/share/cagefs-skeleton/proc/645214/task/645214/fdinfo/4": No such file or directory du: cannot access "./usr/share/cagefs-skeleton/proc/645214/fd/3": No such file or directory du: cannot access "./usr/share/cagefs-skeleton/proc/645214/fdinfo/3": No such file or directory 94G ./usr du: cannot access "./home/virtfs/tldus/usr/share/cagefs-skeleton/proc/645214/task/645214/fd/4": No such file or directory du: cannot access "./home/virtfs/tldus/usr/share/cagefs-skeleton/proc/645214/task/645214/fdinfo/4": No such file or directory du: cannot access "./home/virtfs/tldus/usr/share/cagefs-skeleton/proc/645214/fd/3": No such file or directory du: cannot access "./home/virtfs/tldus/usr/share/cagefs-skeleton/proc/645214/fdinfo/3": No such file or directory du: cannot access "./home/virtfs/tldus/usr/share/cagefs-skeleton/proc/645472": No such file or directory 100G ./home 0 ./media 0 ./mnt 2.6G ./opt 0 ./srv 0 ./backup 7.1G ./jetbackup 2.0G ./local_backup 0 ./local_backup_staging 208G .0 -
So /usr and /home are your largest directories from what I can see here. You can find where the disk allocation is in /usr or /home by moving into one of those directories and running the command again. 0 -
Thank you that helps a lot! 0
Please sign in to leave a comment.
Comments
7 comments