1LVMLOCKCTL(8)                                                    LVMLOCKCTL(8)
2
3
4

NAME

6       lvmlockctl — Control for lvmlockd
7

SYNOPSIS

9       lvmlockctl [options]
10

DESCRIPTION

12       This command interacts with lvmlockd(8).
13

OPTIONS

15       -h|--help
16              Show this help information.
17
18       -q|--quit
19              Tell lvmlockd to quit.
20
21       -i|--info
22              Print lock state information from lvmlockd.
23
24       -d|--dump
25              Print log buffer from lvmlockd.
26
27       -w|--wait 0|1
28              Wait option for other commands.
29
30       -f|--force 0|1
31              Force option for other commands.
32
33       -k|--kill vgname
34              Kill access to the VG when sanlock cannot renew lease.
35
36       -r|--drop vgname
37              Clear locks for the VG when it is unused after kill (-k).
38
39       -E|--gl-enable vgname
40              Tell lvmlockd to enable the global lock in a sanlock VG.
41
42       -D|--gl-disable vgname
43              Tell lvmlockd to disable the global lock in a sanlock VG.
44
45       -S|--stop-lockspaces
46              Stop all lockspaces.
47

USAGE

49       --info This  collects  and displays lock state from lvmlockd.  The dis‐
50              play is primitive, incomplete and will change in future version.
51              To  print  the raw lock state from lvmlockd, combine this option
52              with --dump|-d.
53
54       --dump This collects the circular log buffer of debug  statements  from
55              lvmlockd and prints it.
56
57       --kill This is run by sanlock when it loses access to the storage hold‐
58              ing leases for a VG.  It runs the command specified in  lvm.conf
59              lvmlockctl_kill_command  to  deactivate  LVs  in the VG.  If the
60              specified command is successful, locks will be dropped  for  the
61              VG  in  lvmlockd  (the  equivalent  of lvmlockctl --drop will be
62              run.)  If no command is specified, or the  command  fails,  then
63              the  user must intervene to forcefully deactivate LVs in the VG,
64              and if successful, run lvmlockctl --drop.  For  more,  see  lvm‐
65              lockd(8).
66
67       --drop This should only be run after a VG has been successfully deacti‐
68              vated following an lvmlockctl --kill  command.   It  clears  the
69              stale  lockspace from lvmlockd.  When lvmlockctl_kill_command is
70              used, the --kill command may run drop automatically.  For  more,
71              see lvmlockd(8).
72
73       --gl-enable
74              This enables the global lock in a sanlock VG.  This is necessary
75              if the VG that previously held the global lock is removed.   For
76              more, see lvmlockd(8).
77
78       --gl-disable
79              This  disables  the global lock in a sanlock VG.  This is neces‐
80              sary if the global lock has mistakenly been enabled in more than
81              one  VG.  The global lock should be disabled in all but one san‐
82              lock VG.  For more, see lvmlockd(8).
83
84       --stop-lockspaces
85              This tells lvmlockd to stop all lockspaces.  It can be useful to
86              stop  lockspaces  for  VGs that the vgchange --lock-stop command
87              can no longer see, or to stop the dlm global lockspace which  is
88              not  directly  stopped  by  the  vgchange command.  The wait and
89              force options can be used with this command.
90

SEE ALSO

92       lvm(8), lvmlockd(8)
93
94
95
96Red Hat, Inc           LVM TOOLS 2.03.22(2) (2023-08-02)         LVMLOCKCTL(8)