Boot with disabled qubes autostart so your keyboard and mouse will work in dom0:
The following instructions are valid for Qubes OS R4.0 legacy mode and Qubes OS R4.1 legacy and UEFI modes. For Qubes OS R4.0 in UEFI mode, there is no GRUB, so manual boot from another operating system is needed. In several cases, there is a need to...
Try to start/restart to VM with removed large file a few times.
Qubes OS is keeping one revision for each volume so the large file is still present in the old volume revision.
You can also run fstrim
in your qube and in dom0:
I just moved to qubes and still migrating my old vms to it. I loaded vmdks onto a temporary vault domain. After converting one of them into raw, creating standalone dom and removing copy of raw from the temporary vault, I noticed that now my vault takes 47 GiB, although the /home filesystem on it takes ~26 GiB. Why?
Yes, I removed the raw using rm and there is no wastebasket I am aware of.
Only /home should take space since everything else is a part of the template, right?
p.s. While writing …
My Qubes 4.2 laptop was running fine until yesterday, when I copied about 40GiB into an AppVM and then tried to start another AppVM. The latter was denied, because vm-pool/data went to 92.0% and total disk usage to 90.7% due to the copying. So, I deleted (not just trashed) about 14GiB of the copied data again and issued an fstrim -v /home in that AppVM, which reported to have trimmed only 795,1 MiB, though. However, pool and total disk usage in Qubes Disk Space Monitor did not change …
2 Likes