I buy the argument for attached removable file systems. It looks like
today fstrim iterates over /proc/self/mountinfo and trims all
non-pseudo/non-netfs. On the other hand enough guides on the internet
say that to have a working system with an SSD, you want to have TRIM.
By
not applying the proper defaults, many users will still enable
fstrim.timer and then not think about it when the recovery/forensic
case
comes along. So this is surprising nonetheless.
It feels like fstrim should have a mode that looks at volumes
referenced
by /etc/fstab (just like mount -a, that it wanted to mimic according to
the code) instead of the currently mounted filesystems. And then we
actually should enable that by default.