LVMLOCKCTL(8)

📦
version 2.03.43 · 10 versions
, in centos-stream 10

💅 LVMLOCKCTL(8) — the manual page, but make it group chat

okay so this is lvmlockctl, from the System Manager's Manual section, and honestly? she's the little sidekick to lvmlockd(8) and she's iconic for it. 🎀

✨ NAME

lvmlockctl — the control remote for lvmlockd 🕹️

🦋 SYNOPSIS

lvmlockctl [options]

🌸 DESCRIPTION

bestie, this command talks to lvmlockd(8). that's the whole vibe. it's the way you poke the lock daemon and ask it things, or tell it things, or (respectfully) tell it to log off. 💅

👑 OPTIONS

  • -h, --help — shows you this help info. the "what does this even do" button 🫶
  • -q, --quit — tells lvmlockd to quit. like, bye bestie 💀
  • -i, --info — prints the lock state info straight out of lvmlockd ⭐
  • -d, --dump — prints the log buffer from lvmlockd 🌈
  • -w, --wait 0|1 — the wait option, for the other commands. give it a 0 or a 1 🙈
  • -f, --force 0|1 — the force option, for the other commands. again: 0 or 1, no cap ✨
  • -k, --kill vgname — kills access to the VG when sanlock can't renew the lease 😭 scary but necessary
  • -r, --drop vgname — clears the locks for the VG when it's unused, after a kill (-k) 🧹
  • -E, --gl-enable vgname — tells lvmlockd to enable the global lock in a sanlock VG 🔥
  • -D, --gl-disable vgname — tells lvmlockd to disable the global lock in a sanlock VG 🌙
  • -S, --stop-lockspaces — stops all the lockspaces. all of them. periodt 👑

💜 USAGE

🍓 --info

this one collects and displays the lock state from lvmlockd. heads up though — the display is primitive, incomplete, and may change in future versions, so don't get too attached, she's still growing 🌱

if you wanna see the raw info lines from lvmlockd, combine this option with --dump|-d. very "why not both" of you 💅

each VG lockspace may include lines with these prefixes:

  • "VG" for volume group info
  • "LS" for lockspace info
  • "PR" for persistent reservation fencing info
  • "LK" for lock info
  • "LW" for waiting lock info

iykyk 🎀

🧚 --dump

this collects the circular log buffer of debug statements from lvmlockd and prints it. it's giving receipts 🔍

💀 --kill

okay so this one is run by sanlock when it loses access to the storage holding leases for a VG. it runs the command specified in the lvm.conf lvmlockctl_kill_command setting to deactivate LVs in the VG.

if that specified command is successful, locks will be dropped for the VG in lvmlockd — literally the equivalent of running lvmlockctl --drop. slay ✨

but if no command is specified, or the command fails, then the user has to intervene and forcibly deactivate LVs in the VG, and if that works, run lvmlockctl --drop. for more, see lvmlockd(8) 🫶

not me stressing — this is the "things went sideways" path, so pay attention fr fr

🌈 --drop

this should only be run after a VG has been successfully deactivated following an lvmlockctl --kill command. it clears the stale lockspace from lvmlockd.

when lvmlockctl_kill_command is used, the --kill command may run drop automatically. for more, see lvmlockd(8) ⭐

🔥 --gl-enable

this enables the global lock in a sanlock VG. it's necessary if the VG that previously held the global lock is removed. for more, see lvmlockd(8) 👑

🌙 --gl-disable

this disables the global lock in a sanlock VG. it's necessary if the global lock has mistakenly been enabled in more than one VG — the global lock should be disabled in all but one sanlock VG. for more, see lvmlockd(8) 🙈

👯 --stop-lockspaces

this tells lvmlockd to stop all lockspaces. it can be useful to stop lockspaces for VGs that the vgchange --lockstop command can no longer see, or to stop the dlm global lockspace, which is not directly stopped by the vgchange command.

the wait and force options can be used with this command 💖

🦄 SEE ALSO

that's the whole page bestie, go forth and lock responsibly 🫶✨

Red Hat, Inc. — LVM TOOLS 2.03.43(2)-RHEL10 — (2026-10-13) 🎀 that's the source, the version, and the date, all cute and accounted for. mwah 💋

📦 where this page comes from