You can try using # du -h -d 1 / to locate the largest directory under /. Once you’ve located the largest directory, replace / with that directory. Repeat that until you find the culprit (if there is a single large directory).
EDIT (2024-07-22T19:34Z): As suggested by @[email protected], you can also use a program like Filelight, which provides a visual and more comprehensive breakdown of the sizes of directories.
Whoops! You are correct — I have updated the original comment. I’m not sure why I wrote df instead of du. This is a good example of why one should always be wary of blindly copying commands 😜 It begins to teeter on being potentially disastrous if I had instead wrote dd.
Ah, I see. Just be aware that any additional file size when you get to the stage you can install KDE is pretty much considered the “bloat” part of installs, meaning you only make arch as bloated as you want after that. I like filelight in KDE https://apps.kde.org/filelight/
You can try using
# du -h -d 1 /to locate the largest directory under/. Once you’ve located the largest directory, replace/with that directory. Repeat that until you find the culprit (if there is a single large directory).EDIT (2024-07-22T19:34Z): As suggested by @[email protected], you can also use a program like Filelight, which provides a visual and more comprehensive breakdown of the sizes of directories.
You can use Filelight which is much simpler and more visual.
But it doesn’t make you feel like hackerman
goddamn does it ever feel good to feel like a hackerman
Agreed.
ncdufor the terminal. Also enables you to delete folders/files.gdu is another alternative. It is sometimes faster than ncdu for me.
Df does that too, or did you mean
du?Whoops! You are correct — I have updated the original comment. I’m not sure why I wrote
dfinstead ofdu. This is a good example of why one should always be wary of blindly copying commands 😜 It begins to teeter on being potentially disastrous if I had instead wrotedd.Luckily the syntax wouldn’t have worked if it was
ddYou’re a life saver I finally found the culprit
Do tell! We need a follow up :)
It’s “Steam” inside .local eat up 6GB even though I have not open it yet and tmp files (almost 5GB) that is not clear itself after installing the OS
A fresh Arch install included Steam? Or was this not a fresh install?
I install it during pacstrap
Ah, I see. Just be aware that any additional file size when you get to the stage you can install KDE is pretty much considered the “bloat” part of installs, meaning you only make arch as bloated as you want after that. I like filelight in KDE https://apps.kde.org/filelight/
Or you could use baobab to do the same thing if you want an answer within 10 minutes.
Or dust if you want it fastest with a pretty graph