]>
Commit | Line | Data |
---|---|---|
5951ef33 | 1 | .TH CLVMD 8 "LVM TOOLS #VERSION#" "Red Hat Inc" \" -*- nroff -*- |
ada26433 | 2 | .SH NAME |
f15c75cb | 3 | clvmd \- cluster LVM daemon |
ada26433 PC |
4 | .SH SYNOPSIS |
5 | .B clvmd | |
c63b155d ZK |
6 | .RB [ \-d |
7 | .RI [< value >] | |
8 | .RB [ \-C ]] | |
9 | .RB [ \-E | |
10 | .RI < "lock uuid" >] | |
11 | .RB [ \-f ] | |
12 | .RB [ \-h ] | |
13 | .RB [ \-I | |
14 | .IR "cluster_manager" ] | |
15 | .RB [ \-R ] | |
16 | .RB [ \-S ] | |
17 | .RB [ \-t | |
18 | .RI < timeout >] | |
19 | .RB [ \-T | |
20 | .RI < "start timeout" >] | |
21 | .RB [ \-V ] | |
ada26433 | 22 | .SH DESCRIPTION |
f15c75cb | 23 | clvmd is the daemon that distributes LVM metadata updates around a cluster. |
c63b155d | 24 | It must be running on all nodes in the cluster and will give an error |
f15c75cb | 25 | if a node in the cluster does not have this daemon running. |
ada26433 PC |
26 | .SH OPTIONS |
27 | .TP | |
c63b155d | 28 | .BR \-d [< \fIvalue >] |
be313b13 PC |
29 | Enable debug logging. Value can be 0, 1 or 2. |
30 | .br | |
92e6277c | 31 | 0 disables debug logging |
be313b13 | 32 | .br |
c63b155d | 33 | 1 sends debug logs to stderr (implies \fB\-f\fP option) |
be313b13 PC |
34 | .br |
35 | 2 sends debug logs to syslog | |
36 | .br | |
c63b155d ZK |
37 | If |
38 | .B \-d | |
92e6277c | 39 | is specified without a value then 1 is assumed. |
be313b13 | 40 | .TP |
c63b155d ZK |
41 | .B \-C |
42 | Only valid if | |
43 | .B \-d | |
be313b13 PC |
44 | is also specified. Tells all clvmds in a cluster to enable/disable debug logging. |
45 | Without this switch, only the local clvmd will change its debug level to that | |
c63b155d ZK |
46 | given with |
47 | .B \-d | |
48 | . | |
08152c90 PC |
49 | .br |
50 | This does not work correctly if specified on the command-line that starts clvmd. | |
c63b155d ZK |
51 | If you want to start clvmd |
52 | .B and | |
08152c90 PC |
53 | enable cluster-wide logging then the command needs to be issued twice, eg: |
54 | .br | |
c63b155d | 55 | .B clvmd |
08152c90 | 56 | .br |
c63b155d | 57 | .B clvmd -d2 |
08152c90 | 58 | .br |
ada26433 | 59 | .TP |
c63b155d ZK |
60 | .BR \-E < "\fIlock uuid" > |
61 | Pass lock uuid to be reacquired exclusively when clvmd is restarted. | |
ada26433 | 62 | .TP |
c63b155d ZK |
63 | .B \-f |
64 | Don't fork, run in the foreground. | |
699b275a | 65 | .TP |
c63b155d ZK |
66 | .B \-h |
67 | Show help information. | |
a039e204 | 68 | .TP |
c63b155d ZK |
69 | .B \-I \fIcluster manager |
70 | Selects the cluster manager to use for locking and internal communications, | |
71 | the available managers will be listed as part of the \fBclvmd -h\fP output. | |
72 | clvmd will use the first cluster manager that succeeds, and it checks them | |
73 | in the order cman,corosync,openais. As it is quite possible to have | |
74 | (eg) corosync and cman available on the same system you might have to | |
75 | manually specify this option to override the search. | |
76 | .TP | |
77 | .B \-R | |
be313b13 | 78 | Tells all the running clvmds in the cluster to reload their device cache and |
6ad43b9b PC |
79 | re-read the lvm configuration file. This command should be run whenever the |
80 | devices on a cluster system are changed. | |
81 | .TP | |
c63b155d | 82 | .B \-S |
3ceb7608 AK |
83 | Tells the running clvmd to exit and reexecute itself, for example at the |
84 | end of a package upgrade. The new instance is instructed to reacquire | |
85 | any locks in the same state as they were previously held. (Alternative | |
86 | methods of restarting the daemon have the side effect of changing | |
87 | exclusive LV locks into shared locks.) | |
c407d2bd | 88 | .TP |
c63b155d ZK |
89 | .BR \-t < \fItimeout > |
90 | Specifies the timeout for commands to run around the cluster. This should not | |
91 | be so small that commands with many disk updates to do will fail, so you | |
92 | may need to increase this on systems with very large disk farms. | |
93 | The default is 30 seconds. | |
94 | .TP | |
95 | .BR \-T < "\fIstart timeout" > | |
96 | Specifies the timeout for clvmd daemon startup. If the daemon does not report | |
97 | that it has started up within this time then the parent command will exit with | |
98 | status of 5. This does NOT mean that clvmd has not started! What it means is | |
99 | that the startup of clvmd has been delayed for some reason; the most likely | |
100 | cause of this is an inquorate cluster though it could be due to locking | |
101 | latencies on a cluster with large numbers of logical volumes. If you get the | |
102 | return code of 5 it is usually not necessary to restart clvmd - it will start | |
103 | as soon as that blockage has cleared. This flag is to allow startup scripts | |
104 | to exit in a timely fashion even if the cluster is stalled for some reason. | |
105 | .br | |
106 | The default is 0 (no timeout) and the value is in seconds. Don't set this too | |
107 | small or you will experience spurious errors. 10 or 20 seconds might be | |
108 | sensible. | |
109 | .br | |
110 | This timeout will be ignored if you start clvmd with the -d switch. | |
8b9e5151 | 111 | .TP |
c63b155d | 112 | .B \-V |
f15c75cb | 113 | Display the version of the cluster LVM daemon. |
d2c11605 ZK |
114 | |
115 | .SH ENVIRONMENT VARIABLES | |
116 | .TP | |
117 | .B LVM_CLVMD_BINARY | |
118 | The CLVMD binary to use when clmvd restart is requested. | |
119 | Defaults to #CLVMD_PATH#. | |
120 | .TP | |
121 | .B LVM_BINARY | |
122 | The LVM2 binary to use. Defaults to #LVM_PATH#. | |
123 | ||
ada26433 PC |
124 | .SH SEE ALSO |
125 | .BR lvm (8) |