On Focal Fossa when the fstrim.timer goes off on Monday morning (first boot after midnight) the 'fstrim' command does not 'trim' /home .
I think this may be do to the directive "ProtectHome" being set to "yes" in the "fstrim.service" file . I'll find out in 1 week . If you have your /home on a ssd you might want to 'trim' it manually .
root@linux-desktop:/usr# grep trim /var/log/syslog
May 11 05:57:39 linux-desktop fstrim[1158]: /boot/efi: 449.6 MiB (471474176 bytes) trimmed on /dev/nvme0n1p1
May 11 05:57:39 linux-desktop fstrim[1158]: /: 37.8 GiB (40555507712 bytes) trimmed on /dev/nvme0n1p3
May 11 05:57:39 linux-desktop systemd[1]: fstrim.service: Succeeded.
I looked at a backup of 18.04 and "ProtectHome" was set to "read-only" so thats probably the issue .
I think this may be do to the directive "ProtectHome" being set to "yes" in the "fstrim.service" file . I'll find out in 1 week . If you have your /home on a ssd you might want to 'trim' it manually .
root@linux-desktop:/usr# grep trim /var/log/syslog
May 11 05:57:39 linux-desktop fstrim[1158]: /boot/efi: 449.6 MiB (471474176 bytes) trimmed on /dev/nvme0n1p1
May 11 05:57:39 linux-desktop fstrim[1158]: /: 37.8 GiB (40555507712 bytes) trimmed on /dev/nvme0n1p3
May 11 05:57:39 linux-desktop systemd[1]: fstrim.service: Succeeded.
I looked at a backup of 18.04 and "ProtectHome" was set to "read-only" so thats probably the issue .
Comment