I really don’t get these latest messages and they are adding to my confusion. If the disk trim is important
a) infosec-wise
b) technical-wise (lvm stuff apparently “wanting” fstrim)
then, why is disk trimming not enabled by default with QubesOS?
Since it is not enabled by default, and it seems like it is a vital thing to enable, how exactly do I do this without confusing myself
Check in dom0 and in all VM’s this:
sudo systemctl status fstrim.timer
I have r4.2.4 and it’s activated even on VM that I’ve made yesterday from fresh minimal template in which I’ve manually didn’t start any systemd services.
As far as officially supported TemplateVMs are concerned, they get trimmed automatically now (since Trim filesystems after TemplateVM update by Atrate · Pull Request #619 · QubesOS/qubes-core-agent-linux · GitHub).