Le jeu. 4 nov. 2021 à 16:25, David Teigland <teigland@xxxxxxxxxx> a écrit :
To work around this, you can force the vgchange by skipping the global
lock, and then start the lockspace:
$ vgchange --locktype sanlock --lockopt skipgl svg
WARNING: skipping global lock in lvmlockd.
Logical volume "lvmlock" created.
Volume group "svg" successfully changed
Hi David,
Thanks for the tip.
Using «--lockopt skipgl» worked as expected.
Regards,
Charles
_______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/