DLM_TOOL(8)

💖 NAME 💖

dlm_tool — bestie, this is the little utility that hangs out with the dlm and dlm_controld daemon 🦋 it's your group chat with the daemon basically

---

✨ SYNOPSIS ✨

dlm_tool [COMMAND] [OPTIONS] [ name ]

---

🎀 COMMANDS 🎀

• ls — shows you the dlm_controld internal lockspace state. the inside scoop 💅
• status — dumps the whole dlm_controld daemon state. main character energy, it's giving everything
• dump — dumps the dlm_controld debug buffer
• dump_config — dumps the dlm_controld config settings
• reload_config — reloads the dlm_controld config settings from dlm.conf
• set_config setting=value — sets dlm_controld config settings inside the daemon that's currently running, live, no restart, iconic
• fence_ack nodeid — cancels a waiting fencing operation and just considers it successful. yeah. we're calling it a win 🫶
• log_plock — dumps the dlm_controld plock debug buffer
• plocks lockspace_name — dumps posix locks from dlm_controld for that lockspace
• join lockspace_name — join a lockspace, come through 💃
• leave lockspace_name — leave a lockspace, ok bye 👋
• joinleave lockspace_name — join then immediately leave a lockspace (for testing only.)
• lockdebug lockspace_name — the complete display of locks from the lockspace
• lockdump lockspace_name — minimal display of locks from the lockspace (deprecated ⚠️)
• run command — run the command and check for the result (for lvmlockd only.)
• run_start command — run the command and don't check for the result
• run_check uuid — check the status of a command that was run
• run_cancel uuid — cancel a command that was run and is not yet done
• run_list — dump a list of running commands

---

💅 OPTIONS 💅

• -n — show all node information from dlm_tool ls
• -d 0|1 — resource directory off/on in join, default 0
• -e 0|1 — exclusive create off/on in join, default 0
• -f 0|1 — FS (filesystem) flag off/on in join, default 0
• -i sec — seconds to wait in run_check
• -m mode — permission mode for the lockspace device (octal), default 0600
• -s — summary following lockdebug output (experiemental)
• -v — verbose lockdebug or status output
• -w — wide lockdebug output
• -M — include MSTCPY locks in lockdump output
• -h — print help, then exit
• -V — print program version information, then exit

---

🌸 USAGE 🌸

🌈 fence_ack

Go look at dlm_tool status for the info about waiting fencing operations for specific nodeid's. that's where the tea is ☕

💜 set_config

dlm_tool set_config can change certain config settings in the dlm_controld that's currently running. here's what's supported:

• daemon_debug
• log_debug
• debug_logfile
• plock_debug
• plock_rate_limit
• drop_resources_time
• drop_resources_count
• drop_resources_age
• post_join_delay
• enable_quorum_fencing
• enable_quorum_lockspace
• repeat_failed_fencing

Special cases, for when you wanna revert a previous set_config and restore the previous value (from the default or from dlm.conf):

dlm_tool set_config setting=restore

restores a single setting.

dlm_tool set_config restore_all

restores all settings. the undo button, but make it CLI 💖

🦋 dump_config

A config setting might have been set from any of these: the default, the dlm_controld command line, dlm.conf at startup, dlm.conf from reload_config, or dlm_tool set_config. The dump_config output literally tells you how the values were set:

• setting=value — default value.
• setting=value (cli option) — set from a dlm_controld command line option.
• setting=value (dlm.conf) — set from dlm.conf (at startup or reload.)
• setting=value (set_config) — set from dlm_tool set_config.

---

⭐ EXAMPLES ⭐

💖 dump_config

$ dlm_tool dump_config | head -n 5
daemon_debug=1 (set_config)
foreground=0
log_debug=1 (dlm.conf)
protocol=detect

So in this case, daemon_debug is set by set_config, log_debug is set from dlm.conf, and foreground and protocol are just out here using default values. no notes ✨

💖 set_config

$ dlm_tool dump_config | grep log_debug
log_debug=1 (dlm.conf)

$ dlm_tool set_config "log_debug=0"
set_config done

$ dlm_tool dump_config | grep log_debug
log_debug=0 (set_config)

$ dlm_tool set_config "log_debug=restore"
set_config done

$ dlm_tool dump_config | grep log_debug
log_debug=1 (dlm.conf)

So log_debug is set by dlm.conf (value is 1), then you run set_config to change it to 0, then you use restore to restore it to the dlm.conf setting. the character development 😭

💖 set_config

$ dlm_tool dump_config | grep _debug
daemon_debug=0
log_debug=1 (dlm.conf)
plock_debug=0

$ dlm_tool set_config "daemon_debug=1 log_debug=1 plock_debug=1"
set_config done

$ dlm_tool dump_config | grep _debug
daemon_debug=1 (set_config)
log_debug=1 (set_config)
plock_debug=1 (set_config)

$ dlm_tool set_config "restore_all"
set_config done

$ dlm_tool dump_config | grep _debug
daemon_debug=0
log_debug=1 (dlm.conf)
plock_debug=0

---

👑 SEE ALSO 👑

dlm_controld(8), dlm.conf(5)

---

okay bestie that's the whole page, you're fully caught up, no cap 🧚

this was dlm, dated 2012-04-05, and it lives in section DLM_TOOL(8) of the manual — mwah, go read the friends it shouted out 💜