>>> You should not be running trim in a container/virtual machine
>> Why not? That's, in my case, basically saying "you should not be running
>> trim on a drive exported via iscsi" Perhaps I shouldn't be but I'd like
>> to understand why. Enabling thin_provisioning and fstrim works and gets
>> mapped to the underlying layers all the way down to the SSD.
>
> I guest you didn't understand the systemd timer that runs fstrim on
> the host.
How can the host properly run `fstrim` if it only sees a disk image and
may not know how that image is divided into partitions/filesystems?
Stefan
