Phew 
So I leave everything as it is. The 97% is not a problem.
No, the outcome is the same with or without /
Hm…
Try: sudo dust -b -D -d 1 -x /home/jonathan/
EDIT: Sorry, I was misinterpreting the output you showed above by thinking you did only get 2 or three lines of output when running dust
Where do you see 97%?
I just guess it shows the largest item in red and the total sum
In the disk-usage app:
“moduli” and “services” use the most space.
❯ sudo du -sh /etc/* | sort -h
...
584K /etc/ssh
688K /etc/services
820K /etc/systemd
2,9M /etc/bazaar
3,6M /etc/brltty
6,0M /etc/pki
14M /etc/udev
27M /etc/selinux
I removed brltty (because I don’t use braille) and bazaar (first took a backup). And altough I deleted those “big” files, it’s still 97%…
...
688K /etc/services
820K /etc/systemd
6,0M /etc/pki
14M /etc/udev
27M /etc/selinux
❯ sudo dust -b -D -d 1 -x /home/jonathan/
0B ┌── .cert
0B ├── .cups
0B ├── Applications
0B ├── Documenten
0B ├── Mixxx
4.0K ├── .somafm-radio
4.0K ├── .swt
8.0K ├── .gnupg
12K ├── .logseq
16K ├── .ssh
20K ├── .hydrogen
68K ├── .pki
84K ├── .bluefish
168K ├── .openshot_qt
216K ├── .dotnet
232K ├── .vst3
236K ├── .java
1.1M ├── Schermopnamen
1.6M ├── .npm
2.1M ├── Documents
13M ├── .vst
13M ├── .eclipse
27M ├── .BitwigStudio
30M ├── BespokeSynth
30M ├── .eteks
54M ├── .zotero
64M ├── .m2
94M ├── Afbeeldingen
118M ├── .cargo
120M ├── WebCam
150M ├── .vscode
200M ├── pacemaker
253M ├── midilink
286M ├── .config
350M ├── Downloads
542M ├── OneDrive
708M ├── .sdkman
757M ├── Muziek
1.3G ├── .rustup
1.4G ├── Sync
1.7G ├── .wine
1.8G ├── .mozilla
1.9G ├── .cache
3.1G ├── Zotero
7.7G ├── Piraat
11G ├── .mixxx
20G ├── .local
28G ├── vms
51G ├── Nextcloud
111G ├── .var
246G ┌─┴ jonathan
I don’t know this disk app.
df -h didn’t show anything high like this.
You have a lot of stuff in ~/.varwhich is, AFAIK, only flatpak stuff.
You could look what uses the most space by running
du -sh ~/.var/app/ | sort -h
But, as I said above, you have (looking at the df output) enough free space.
It’s a big difference. sudo du -sh /etc/* shows
6,0M /etc/pki
14M /etc/udev
27M /etc/selinux
which is even bigger then the moduli and services the app shows.
As long as everything seems to work…
I had some strange beeping coming from my FrameWork laptop and it happened once or twice that it booted where I had to choose the latest image. But apart from that, everything runs nice 
One thing to note about the Disk Usage application (and any disk space application) is that if you are running it as a Flatpak it will run in a sandboxed environment and the /etc it sees is not you computer’s actual /etc.
Additionally by default the flatkpak does not have access to your entire host system which makes disk usage applications difficult to use.
Even if you specify that the flatpak can see your whole system, your computer’s /etc will likely be mounted under /run/host/etc (I… think but am not sure… it definitely mounts it somewhere odd) and the /etc you see in Disk Usage will still point to the sandboxed environment.
TL;DR: if a Flatpak application says /etc is 97% full that is the sandbox environment and unrelated to your host system.
1 Like
This means that those flatpak disk usage apps are mor or less useless.
I never ran a GUI disk usage app because I like what I can do on the command line.
For checking system space the flatpak disk usage applications are fairly usage. Even if you give it access to the host system it tends to get confused on the mount points… it’s a mess.
It can be useful if you are looking for what is taking up space in your $HOME (~) folder but that’s about it.
There are people who get more use out of the graphical interface. I salute your knowledge and experience with the terminal but there is a learning curve involved.
If the goal is to get system-wide “what is using up space” information via a Disk Usage application, one will most likely want to layer it (via rpm-ostree). Layering too many packages can cause headaches on updates and is generally not recommended, so if one only needs Disk Usage a few times a year an argument can be made for layering it, using it, and then removing the layer.
Thanks for clarifying that! I’ll use the terminal for disk usage then, from now on!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.