2. EL 7
  3. resource-agents
  4. ocf_heartbeat_lvmlockd(7)

Scroll to navigation

OCF_HEARTBEAT_LVMLOC(7) OCF resource agents OCF_HEARTBEAT_LVMLOC(7)

NAME

ocf_heartbeat_lvmlockd - This agent manages the lvmlockd daemon

SYNOPSIS

lvmlockd [start | stop | monitor | meta-data | validate-all]

DESCRIPTION

This agent manages the lvmlockd daemon. "lvmlockd" is like "clvmd". Both are used by LVM commands to coordinate access to shared storage, but with different design and implementations. "lvmlockd" can use two lock managers: dlm and sanlock. This agent only supports "dlm + lvmlockd". If dlm (or corosync) are already being used by other cluster software, you are advised to select dlm, then configure "controld" resource agent for dlm and this agent for "lvmlockd". Otherwise, consider sanlock for "lvmlockd" if dlm/corosync is not required.

Using lvmlockd requires the settings in LVM configuration file (/etc/lvm/lvm.conf): "locking_type = 1" and "use_lvmlockd = 1". This RA will change the settings respectively if needed.

For more information, refer to manpage lvmlockd.8.

SUPPORTED PARAMETERS

with_cmirrord

Start with cmirrord (cluster mirror log daemon).

(optional, boolean, default false)

pidfile

pid file

(optional, string, default "/run/lvmlockd.pid")

socket_path

Set the socket path to listen on.

(optional, string, default "/run/lvm/lvmlockd.socket")

syslog_priority

Write log messages from this level up to syslog.

(optional, string, default "warning")

adopt

Adopt locks from a previous instance of lvmlockd.

(optional, integer, default 1)

SUPPORTED ACTIONS

This resource agent supports the following actions (operations):

start

Starts the resource. Suggested minimum timeout: 90s.

stop

Stops the resource. Suggested minimum timeout: 90s.

monitor

Performs a detailed status check. Suggested minimum timeout: 90s. Suggested interval: 30s.

meta-data

Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 10s.

validate-all

Performs a validation of the resource configuration. Suggested minimum timeout: 20s.

EXAMPLE CRM SHELL

The following is an example configuration for a lvmlockd resource using the crm(8) shell:

primitive p_lvmlockd ocf:heartbeat:lvmlockd \


  op monitor timeout="90s" interval="30s" depth="0"

EXAMPLE PCS

The following is an example configuration for a lvmlockd resource using pcs(8)

pcs resource create p_lvmlockd ocf:heartbeat:lvmlockd \


  op monitor timeout="90s" interval="30s" depth="0"

SEE ALSO

http://clusterlabs.org/

AUTHOR

ClusterLabs contributors (see the resource agent source for information about individual authors)

03/19/2024 resource-agents UNKNOWN