OCF_HEARTBEAT_LVM-A(7) | OCF resource agents | OCF_HEARTBEAT_LVM-A(7) |
ocf_heartbeat_LVM-activate - This agent activates/deactivates logical volumes.
LVM-activate [start | stop | monitor | meta-data | validate-all]
This agent manages LVM activation/deactivation work for a given volume group.
It supports the following modes, controlled by the vg_access_mode parameter:
* lvmlockd * system_id * clvmd * tagging
Notes:
1. There are two possible configuration combinations: lvmlockd+LVM-activate and clvm+LVM-activate. However, it is not possible to use both at the same time!
2. Put all "lvmlockd"/"clvmd" volume groups into auto management by the agent if using the cluster to manage at least one of them. If you manage some manually, the stop action of the lvmlockd agent may fail and the node may get fenced, because some DLM lockspaces might be in use and cannot be closed automatically.
vgname
(unique, required, string, no default)
lvname
(optional, string, no default)
vg_access_mode
(required, string, no default)
activation_mode
This option only has effect on "lvmlockd"/"clvmd" vg_access_mode. For "system_id" and "tagging", they always mean exclusive activation.
(optional, string, default "exclusive")
tag
(optional, string, default "pacemaker")
This resource agent supports the following actions (operations):
start
stop
monitor
meta-data
validate-all
The following is an example configuration for a LVM-activate resource using the crm(8) shell:
primitive p_LVM-activate ocf:heartbeat:LVM-activate \
params \
vgname=string \
vg_access_mode=string \
op monitor timeout="90s" interval="30s" depth="0"
The following is an example configuration for a LVM-activate resource using pcs(8)
pcs resource create p_LVM-activate ocf:heartbeat:LVM-activate \
vgname=string \
vg_access_mode=string \
op monitor timeout="90s" interval="30s" depth="0"
http://clusterlabs.org/
ClusterLabs contributors (see the resource agent source for information about individual authors)
06/27/2020 | resource-agents UNKNOWN |