Hello all.
I am aware the issue of configuring LVM-Thin in a clustered environment with shared storage has been extensively discussed and why it is a really bad idea.
However, l would like to ask this question from a different angle. When looking into our SAN storage configuration, there is an option to utilize Thin provisioning at the SAN level (attached image). This led me to thinking whether configuring such provisioned volume as (regular Thick) LVM storage on Proxmox level is viable.
Multipath iSCSI in place; mpath pv dev / vg on PVE.
So with a configuration where VM is assigned a 100 GB disk from LVM PVE storage of which 20 GB is used, hosted on LVM-Thin SAN LUN, only those 20 GB are indeed actually consumed from the SAN.
Does this approach work or is it still in violation of 'single-writer' principle?
Thank you.

I am aware the issue of configuring LVM-Thin in a clustered environment with shared storage has been extensively discussed and why it is a really bad idea.
However, l would like to ask this question from a different angle. When looking into our SAN storage configuration, there is an option to utilize Thin provisioning at the SAN level (attached image). This led me to thinking whether configuring such provisioned volume as (regular Thick) LVM storage on Proxmox level is viable.
Multipath iSCSI in place; mpath pv dev / vg on PVE.
So with a configuration where VM is assigned a 100 GB disk from LVM PVE storage of which 20 GB is used, hosted on LVM-Thin SAN LUN, only those 20 GB are indeed actually consumed from the SAN.
Does this approach work or is it still in violation of 'single-writer' principle?
Thank you.
