I’m noticing that an AppVM is huge - even though it shouldn’t be - there is almost nothing in /home, /usr/local, etc.
However, one thing I know: My setup has a few symlinks in /home/user/ that point to some huge items in the root.
But should this really cause the AppVM size to bloat? The symlinks themselves are very small, after all. (I’m looking at the size in the Qubes Manager after the AppVM has shut down)
I do recall a time where symlinks in /home/user pointing to larger items in root didn’t bloat my AppVM size - but at some point this started happening.
/rw is the mountpoint for the private volume’s filesystem containing the AppVM’s data. E.g. /home is bind mounted from /rw/home.
fstrim told the storage system in dom0 which parts the VM filesystem currently considers to be unused, so that they can be discarded.
Did you maybe divide the byte size by 1000^2? One MiB as shown in Qube Manager is 1024^2.
Probably.
/rw is mounted with the discard mount option, so normally data is discarded automatically. But I think this could get out of sync in case of a crash (or maybe even a regular shutdown) right after deleting some files.
VMs also come with a systemd unit fstrim.timer that runs a VM-wide fstrim command. Ideally this should catch cases like yours where the VM’s and dom0’s view of unused data went out of sync, but it’s scheduled “weekly” and if it’s in a short-running VM I’m not sure if the timer will ever really trigger.