What command output(s) show(s) are using more disk space than you believe you are?
I ask this because in the default install, thin volumes are used, so it is not clear if you are noting that the filesystem is more full, the thin pool is more full, or the volume group is more full than expected.
I was making veracrypt vaults in dom0, and testing making them under different file permissions, user privileges, hidden, and overt…and in less than kosher spaces on the hd.
Some of those vaults ended up with circular binds… and just simply disappeared.
I think those vaults are the problem. My dom0 space is all but gone… despite clearing out any unnecessary data.
Veracrypt is giving me available space each time I make/test a vault. And so far, deleting the vaults, clearing trash, rebooting, doesn’t give Veracrypt access to the freed storage. The disk usage GUI doesn’t jive with Veracrypt.
Then look for lines with “G” (GB) or “M” (MB) larger than expected.
Navigate down to that directory and use the command again.
In my case, /usr is large, but that’s expected. Most of that is /usr/lib, expected.
In my case, /var is large. Is that expected? Again, most of that is /var/lib, expected.
/var/log tends to be where my dom0 filesystem grows. Even with the more recent qubes work to trim logs, it grows faster than I’d like, so I have scripts to clean it out.
You can use this method to search and destroy your space wasters.
This is interesting to me. Your dom0 root filesystem is ~20GB, but the thin pool for dom0 is 24GB. Is there more than one volume in the root-pool? If not, perhaps auto-extension occurred, but filesystem has not been extended?
I can’t see one, and I didn’t set one up.
I’ve been hacking away at plenty of things just to learn Qubes… so not too big of a loss if I have to reinstall. But for future it would be nice to know what I did to cause this anomaly (particularly the disappearing vaults).
Nope, but here’s a sanitized version - this is for R4.0, probably needs a review for R4.1.
#!/bin/bash
# remove all logs and detritus
sudo sh -c "rm -rf /var/log/xen/console/guest-*"
sudo sh -c "rm -rf /var/log/xen/console/hypervisor.log-*"
sudo sh -c "rm -rf /var/log/libvirt/libxl/*"
sudo sh -c "rm -rf /var/log/qubes/guid.*"
sudo sh -c "rm -rf /var/log/qubes/pacat.*"
sudo sh -c "rm -rf /var/log/qubes/qrexec.*"
sudo sh -c "rm -rf /var/log/qubes/qubesdb.*"
sudo sh -c "rm -rf /var/log/qubes/vm-*"
sudo sh -c "rm -rf /var/log/qubes/mgmt-*"
# sudo sh -c "rm -rf /var/log/qubes/qmemman.log" # does not seem to get recreated until after reboot - skipping to be safe
# sudo sh -c "rm -rf /var/log/qubes/qubes.log" # does not seem to get recreated until after reboot - skipping to be safe
sudo journalctl --vacuum-files=1 1> /dev/null 2> /dev/null
sudo fstrim -av 1> /dev/null 2> /dev/null
echo ""
echo "Completed cleanup log files and similar."
echo ""
They just did a major update I hear… and so far, I haven’t seen any bugs that would make me want to go back to XFCE.
Give it a spin… (you’ll thank me later