On 2/26/24 14:40, Tim Woodall wrote:
On Mon, 26 Feb 2024, Gremlin wrote:
Are you using systemd ?
No, I'm not
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.
My underlying VG is less than 50% occupied, so I can trim the free space
by creating a LV and then removing it again (I have issue_discards set)
FWIW, I did issue fstrim in the VMs with no visible issues at all.
Perhaps I got lucky?
Here is some info: https://wiki.archlinux.org/title/Solid_state_drive
I don't see VM or virtual machine anywhere on that page.
Exactly, and you should not be running it in a VM/container. Which BTW
systemd will not run fstrim in a container.
The Host system takes care of it
Well you can keep shooting yourself in the butt as long as you wish, I
on the other hand tend not to do that as much I possibly can as I need
to be able to set down at times.
