diff --git a/xml/ha_cluster_lvm.xml b/xml/ha_cluster_lvm.xml index a877c45bc..412d2733c 100644 --- a/xml/ha_cluster_lvm.xml +++ b/xml/ha_cluster_lvm.xml @@ -258,18 +258,47 @@ - Use shared activation mode for &ocfs; and add it to the cloned - g-storage group: + Use shared activation mode for &ocfs;: &prompt.root;crm configure primitive vg1 LVM-activate \ params vgname=vg1 vg_access_mode=lvmlockd activation_mode=shared \ op start timeout=90s interval=0 \ op stop timeout=90s interval=0 \ - op monitor interval=30s timeout=90s -&prompt.root;crm configure modgroup g-storage add vg1 + op monitor interval=30s timeout=90s + + + Make sure the VG can only be activated on nodes where the DLM resource + is already running: + + + + + For a single VG using shared activation mode, you can add the VG + to the cloned g-storage group, which already has + internal colocation and order constraints: + +&prompt.root;crm configure modgroup g-storage add vg1 + + + + For a single VG using exclusive activation mode, add constraints directly: + +&prompt.root;crm configure colocation col-vg-with-dlm inf: vg1 cl-dlm +&prompt.root;crm configure order o-dlm-before-vg Mandatory: cl-dlm vg1 + + + + For multiple VGs using either activation mode, you can add constraints + that apply to batches of resources: + +&prompt.root;crm configure colocation col-vg-with-dlm inf: ( vg1 vg2 ) cl-dlm +&prompt.root;crm configure order o-dlm-before-vg Mandatory: cl-dlm ( vg1 vg2 ) + + + Check if the resources are running well: