1OCF_HEARTBEAT_LVM-A(7) OCF resource agents OCF_HEARTBEAT_LVM-A(7)
2
3
4
6 ocf_heartbeat_LVM-activate - This agent activates/deactivates logical
7 volumes.
8
10 LVM-activate [start | stop | monitor | meta-data | validate-all]
11
13 This agent manages LVM activation/deactivation work for a given volume
14 group.
15
16 It supports the following modes, controlled by the vg_access_mode
17 parameter:
18
19 * lvmlockd * system_id * clvmd * tagging
20
21 Notes:
22
23 1. There are two possible configuration combinations:
24 lvmlockd+LVM-activate and clvm+LVM-activate. However, it is not
25 possible to use both at the same time!
26
27 2. Put all "lvmlockd"/"clvmd" volume groups into auto management by the
28 agent if using the cluster to manage at least one of them. If you
29 manage some manually, the stop action of the lvmlockd agent may fail
30 and the node may get fenced, because some DLM lockspaces might be in
31 use and cannot be closed automatically.
32
34 vgname
35 The volume group name.
36
37 (required, string, no default)
38
39 lvname
40 If set, only the specified LV will be activated.
41
42 (optional, string, no default)
43
44 vg_access_mode
45 This option decides which solution will be used to protect the
46 volume group in cluster environment. Optional solutions are:
47 lvmlockd, clvmd, system_id and tagging.
48
49 (required, string, no default)
50
51 activation_mode
52 The activation mode decides the visibility of logical volumes in
53 the cluster. There are two different modes: "shared" for cluster
54 filesystem and "exclusive" for local filesystem. With "shared", an
55 LV can be activated concurrently from multiple nodes. With
56 "exclusive", an LV can be activated by one node at a time.
57
58 This option only has effect on "lvmlockd"/"clvmd" vg_access_mode.
59 For "system_id" and "tagging", they always mean exclusive
60 activation.
61
62 (optional, string, default "exclusive")
63
64 tag
65 The tag used for tagging activation mode.
66
67 (optional, string, default "pacemaker")
68
69 partial_activation
70 If set, the volume group will be activated partially even with some
71 physical volumes missing. It helps to set to true when using
72 mirrored logical volumes.
73
74 (optional, string, default "false")
75
77 This resource agent supports the following actions (operations):
78
79 start
80 Starts the resource. Suggested minimum timeout: 90s.
81
82 stop
83 Stops the resource. Suggested minimum timeout: 90s.
84
85 monitor
86 Performs a detailed status check. Suggested minimum timeout: 90s.
87 Suggested interval: 30s.
88
89 meta-data
90 Retrieves resource agent metadata (internal use only). Suggested
91 minimum timeout: 10s.
92
93 validate-all
94 Performs a validation of the resource configuration. Suggested
95 minimum timeout: 20s.
96
98 The following is an example configuration for a LVM-activate resource
99 using the crm(8) shell:
100
101 primitive p_LVM-activate ocf:heartbeat:LVM-activate \
102 params \
103 vgname=string \
104 vg_access_mode=string \
105 op monitor timeout="90s" interval="30s" depth="0"
106
108 The following is an example configuration for a LVM-activate resource
109 using pcs(8)
110
111 pcs resource create p_LVM-activate ocf:heartbeat:LVM-activate \
112 vgname=string \
113 vg_access_mode=string \
114 op monitor timeout="90s" interval="30s" depth="0"
115
117 http://clusterlabs.org/
118
120 ClusterLabs contributors (see the resource agent source for information
121 about individual authors)
122
123
124
125resource-agents UNKNOWN 10/23/2019 OCF_HEARTBEAT_LVM-A(7)