Hi, We've a config option 'report_discard_supported'[1] which can be added to cinder.conf that will enable trim/unmap support. Also I would like to suggest not creating new openstack-discuss threads for the same issue and reuse the first one created. As I can see these are the 3 threads for the same issue[2][3][4]. [1] https://docs.openstack.org/cinder/latest/configuration/block-storage/config-... [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031789.... [3] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031797.... [4] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031805.... Thanks Rajat Dhasmana On Tue, Jan 17, 2023 at 8:57 AM A Monster <amonster369@gmail.com> wrote:

I deployed openstack using kolla ansible, and used LVM as storage backend for my cinder service, however I noticed that the lvm thin pool size keeps increasing even though the space used by instances volumes is the same, and after a bit of investigating I found out that I had to enable fstrim because the data deleted inside the logical volumes was still allocated from the thin pool perspective and I had to do fstrim on those volumes,

how can I enable this automatically in openstack?