OCF_HEARTBEAT_LVMLOC(7)

💖 NAME 💖

okay bestie, welcome to OCF_HEARTBEAT_LVMLOC(7), brought to you by the OCF resource agents crew. this page is for ocf_heartbeat_lvmlockd, and it manages the lvmlockd daemon — that's the whole name-and-mission combo. periodt. 💅

🦋 SYNOPSIS 🦋

the invocation vibe check is literally:

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

🌸 DESCRIPTION 🌸

okay so 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 the "controld" resource agent for dlm and this agent for "lvmlockd". otherwise, consider sanlock for "lvmlockd" if dlm/corosync is not required. fr fr, that's the whole lock-manager situation. 🫶

using lvmlockd requires the settings in the LVM configuration file (/etc/lvm/lvm.conf): "locking_type = 1" and "use_lvmlockd = 1". this RA will change the settings respectively if needed — highkey obsessed with how it handles that. ✨

for more information, refer to manpage lvmlockd.8. iykyk. 💜

🎀 SUPPORTED PARAMETERS 🎀

here's the full parameter squad, bestie — every single one, no skips, and yes it ate:

• pidfile — pid file. it's optional, type string, default "/run/lvmlockd.pid". 🍓
• socket_path — Set the socket path to listen on. it's optional, type string, default "/run/lvm/lvmlockd.socket". 🔥
• syslog_priority — Write log messages from this level up to syslog. it's optional, type string, default "warning". ⭐
• adopt — Adopt locks from a previous instance of lvmlockd. it's optional, type integer, default 1. 👑

✨ SUPPORTED ACTIONS ✨

this resource agent supports the following actions (operations), and yes, the timeouts are part of the lore:

• 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" OCF_CHECK_LEVEL="0"

🔗 SEE ALSO 🔗

• http://clusterlabs.org/

👑 AUTHOR 👑

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

---

xoxo bestie — source/version resource-agents UNKNOWN, date 10/01/2026, signing off as OCF_HEARTBEAT_LVMLOC(7). 💅💖