FC San with lvm-thin in a Cluster

wne

New Member
Mar 31, 2024
1
0
1
Dear all,

I have connected an FC SAN using lvm-thin (because of the snapshots). At the moment, I am connecting the nodes so that they only see one LUN each. Is there a way to configure the locking so that the LUNs are visible to both hosts? A cold migration between the hosts would be perfectly sufficient for me.

If this is not possible at the moment, are there any plans to implement something similar in the near future?

Best Wolfgang
 
This is NOT supported for shared storage like FC attached SAN since LVM/thin is NOT cluster aware. Your setup is screaming for dataloss, so please don't run anything important on it before rebuilding it in a supported way. Beginning with PVE9 there is snapshot support for LVM/thick which is supported on shared storage:
https://pve.proxmox.com/wiki/Storage has more iinformation on the different storage options and their limits.

@bbgeek17 did a great writeup too although it wasn't updated for PVE9 so the limitation for snapshots doesn't apply anymore: https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/
 
Last edited:
Dear all,

I have connected an FC SAN using lvm-thin (because of the snapshots). At the moment, I am connecting the nodes so that they only see one LUN each. Is there a way to configure the locking so that the LUNs are visible to both hosts? A cold migration between the hosts would be perfectly sufficient for me.

If this is not possible at the moment, are there any plans to implement something similar in the near future?

Best Wolfgang
you can't with lvm-thin, because the metadata volume can't be shared. You need to use classic LVM (and snapshot have been added in pve9 for them)
 
  • Like
Reactions: Johannes S
There are no plans to support LVM Thin for shared storage infrastructure.

I might be wrong but I remember @spirit (as main developer of the LVM/thick-Snapshot support) mentioned that his approach should work too to allow thin provisioning on LVM/thick and might be implemented at some point. I might be wrong though :)