I freed 30GB using Filelight
-
The always huge and killing my system space:
- pacman cache
- docker bullshit
- flatpaks
- journalctl files!
In case you don't already know about it, paccache (part of the pacman-contrib package) will let you easily remove old packages from the pacman cache
-
And that's all, I'm happy since I was out of space.
-
My little widget to get the weather, Blazing Fast Uber Duper made in Rust, has like 85 total dependencies from like 3 crates that I need...
My own software is a hard pass for myself...
That's great!
Another thing that is great, since we are talking about disk space: people, check your Rust repositiry, it might be huge.
I deleted that folder and, in my case, freed 12gb. Not too shabby.
-
Ncdu is my go-to tool. Can't live without it on the servers I administer. However from this thread I've also learned about gdu and diskonaut, that I need to check out.
-
I'm à qdirstat guy : https://github.com/shundhammer/qdirstat
I believe FileLight (in OP above) is a fork of or built on top of QDirstat.
-
And that's all, I'm happy since I was out of space.
I like Bleachbit but I'll check this out
-
Clean all the cache downloads of Arch Linux Packages
pacman -Scc
Remove unused docker networks and images
docker system prune --all
Cleanup untracked git files that might be in .gitignore such as build and out directories (beware of losing data, use "n" instead of "f" for a dry run)
git clean -xdf
Do an aggresive pruning of objects in git (MIGHT BE VERY SLOW)
git gc --aggressive --prune=now
Remove old journal logs, keeping last seven days
journalctl --vacuum-time 7days
Remove pip cache
pip cache purge
I can see you're not using Flatpak, the destroyer of disk space. Nice list though!
-
Personally I'm loving diskonaut. "Graphical" representation but at, ahem, terminal velocity.
I use dua, but this looks neat too.
-
I use
du -hs * | sort -hdu -sxk | sort -ngotta find those hidden files too! -
And that's all, I'm happy since I was out of space.
My dad's Linux setup couldn't log in. After a bit of investigation, starting the session manually and so on, i got a hunch and indeed; i saw in Baobab that the backup script took the wrong disk, filled up the one with home, making it slow, so the log-in thingie timed out, failing the session.
-
On gtk desktops it's something like Baobab. Too sad that the big guys can't make lightweight and standalone software.
-
dustYes, it's
duin Rust + more.Isn't that a wayland notification daemon already?
Edit: no, that's dunst.
Btw, how do you do the background color thing?
-
Isn't that a wayland notification daemon already?
Edit: no, that's dunst.
Btw, how do you do the background color thing?
I was confused what you meant by background colour thing so I went to
dustdocs haha.Now I got you. It's a codeblock so it shows in monospace font. Look up .md formatting for tips.
In this case its a word between backticks `
-
I was confused what you meant by background colour thing so I went to
dustdocs haha.Now I got you. It's a codeblock so it shows in monospace font. Look up .md formatting for tips.
In this case its a word between backticks `
Ah, right, it's the
inline code. Mindslip. Thanks! -
Personally I'm loving diskonaut. "Graphical" representation but at, ahem, terminal velocity.
Jesus, that rustup folder is HUGE
-
Personally I'm loving diskonaut. "Graphical" representation but at, ahem, terminal velocity.
-
flatpak install flathub org.kde.filelight
-
https://github.com/imsnif/diskonaut
No package for my distro, I "installed" an AppImage with AM (which is also how I discovered it)
-
I freed 50gb by running 'docker system prune'...
I'm new to docker and all of my shit stopped working recently. Just wouldn't load. Took about a half hour to find out that old images were taking up about 63GB on my 100GB boot partition, resulting in it being completely full.
I added the command to prune 3 month old images to my update scripts.
-
[moonpie@osiris ~]$ du -h $(which filelight) 316K /usr/bin/filelightK = kilobytes.
[moonpie@osiris ~]$ pacman -Ql filelight | awk '{print $2}' | xargs du | awk '{print $1}' | paste -sd+ | bc 45347740(45347740 bytes is 43.247 megabytes).
KDE packages have many dependencies, which cause the packages themselves to be extremely tiny. By sharing a ton of code via libraries, they save a lot of space.
