[linux-lvm] lvmlockd: about the limitation on lvresizing the LV active on multiple nodes
zren at suse.com
Thu Dec 28 10:42:07 UTC 2017
I see there is a limitation on lvesizing the LV active on multiple node.
>From `man lvmlockd`:
limitations of lockd VGs
* resizing an LV that is active in the shared mode on multiple hosts
It seems a big limitation to use lvmlockd in cluster:
c1-n1:~ # lvresize -L-1G vg1/lv1
WARNING: Reducing active logical volume to 1.00 GiB.
THIS MAY DESTROY YOUR DATA (filesystem etc.)
Do you really want to reduce vg1/lv1? [y/n]: y
LV is already locked with incompatible mode: vg1/lv1
Node "c1-n1" is the last node having vg1/lv1 active on it.
Can we change the lock mode from "shared" to "exclusive" to
lvresize without having to deactivate the LV on the last node?
It will reduce the availability if we have to deactivate LV on all
nodes to resize. Is there plan to eliminate this limitation in the
More information about the linux-lvm