]>
Commit | Line | Data |
---|---|---|
52826846 | 1 | .\" -*- nroff -*- |
90fc992e NB |
2 | ''' Copyright Neil Brown and others. |
3 | ''' This program is free software; you can redistribute it and/or modify | |
4 | ''' it under the terms of the GNU General Public License as published by | |
5 | ''' the Free Software Foundation; either version 2 of the License, or | |
6 | ''' (at your option) any later version. | |
7 | ''' See file COPYING in distribution for details. | |
6a067160 | 8 | .TH MDADM 8 "" v2.6.4 |
52826846 | 9 | .SH NAME |
9a9dab36 | 10 | mdadm \- manage MD devices |
cd29a5c8 | 11 | .I aka |
93e790af | 12 | Linux Software RAID |
cd29a5c8 | 13 | |
52826846 NB |
14 | .SH SYNOPSIS |
15 | ||
e0d19036 | 16 | .BI mdadm " [mode] <raiddevice> [options] <component-devices>" |
52826846 | 17 | |
2ae555c3 | 18 | .SH DESCRIPTION |
52826846 | 19 | RAID devices are virtual devices created from two or more |
cd29a5c8 | 20 | real block devices. This allows multiple devices (typically disk |
35cc5be4 | 21 | drives or partitions thereof) to be combined into a single device to |
cd29a5c8 | 22 | hold (for example) a single filesystem. |
2d465520 | 23 | Some RAID levels include redundancy and so can survive some degree of |
cd29a5c8 NB |
24 | device failure. |
25 | ||
2d465520 NB |
26 | Linux Software RAID devices are implemented through the md (Multiple |
27 | Devices) device driver. | |
cd29a5c8 NB |
28 | |
29 | Currently, Linux supports | |
30 | .B LINEAR | |
31 | md devices, | |
32 | .B RAID0 | |
33 | (striping), | |
34 | .B RAID1 | |
35 | (mirroring), | |
d013a55e NB |
36 | .BR RAID4 , |
37 | .BR RAID5 , | |
98c6faba | 38 | .BR RAID6 , |
1a7dfc35 | 39 | .BR RAID10 , |
b5e64645 | 40 | .BR MULTIPATH , |
cd29a5c8 | 41 | and |
b5e64645 | 42 | .BR FAULTY . |
d013a55e | 43 | |
a9d69660 NB |
44 | .B MULTIPATH |
45 | is not a Software RAID mechanism, but does involve | |
93e790af | 46 | multiple devices: |
d013a55e NB |
47 | each device is a path to one common physical storage device. |
48 | ||
a9d69660 NB |
49 | .B FAULTY |
50 | is also not true RAID, and it only involves one device. It | |
b5e64645 | 51 | provides a layer over a true device that can be used to inject faults. |
52826846 | 52 | |
a9d69660 NB |
53 | '''.B mdadm |
54 | '''is a program that can be used to create, manage, and monitor | |
55 | '''MD devices. As | |
56 | '''such it provides a similar set of functionality to the | |
57 | '''.B raidtools | |
58 | '''packages. | |
59 | '''The key differences between | |
60 | '''.B mdadm | |
61 | '''and | |
62 | '''.B raidtools | |
63 | '''are: | |
64 | '''.IP \(bu 4 | |
65 | '''.B mdadm | |
66 | '''is a single program and not a collection of programs. | |
67 | '''.IP \(bu 4 | |
68 | '''.B mdadm | |
69 | '''can perform (almost) all of its functions without having a | |
70 | '''configuration file and does not use one by default. Also | |
71 | '''.B mdadm | |
72 | '''helps with management of the configuration | |
73 | '''file. | |
74 | '''.IP \(bu 4 | |
75 | '''.B mdadm | |
76 | '''can provide information about your arrays (through Query, Detail, and Examine) | |
77 | '''that | |
78 | '''.B raidtools | |
79 | '''cannot. | |
80 | '''.P | |
81 | '''.I mdadm | |
82 | '''does not use | |
83 | '''.IR /etc/raidtab , | |
84 | '''the | |
85 | '''.B raidtools | |
86 | '''configuration file, at all. It has a different configuration file | |
98b24a2a | 87 | '''with a different format and a different purpose. |
52826846 NB |
88 | |
89 | .SH MODES | |
8382f19b | 90 | mdadm has several major modes of operation: |
cd29a5c8 NB |
91 | .TP |
92 | .B Assemble | |
93e790af | 93 | Assemble the components of a previously created |
52826846 | 94 | array into an active array. Components can be explicitly given |
2ae555c3 | 95 | or can be searched for. |
9a9dab36 | 96 | .B mdadm |
cd29a5c8 NB |
97 | checks that the components |
98 | do form a bona fide array, and can, on request, fiddle superblock | |
99 | information so as to assemble a faulty array. | |
100 | ||
101 | .TP | |
102 | .B Build | |
a9d69660 NB |
103 | Build an array that doesn't have per-device superblocks. For these |
104 | sorts of arrays, | |
105 | .I mdadm | |
106 | cannot differentiate between initial creation and subsequent assembly | |
107 | of an array. It also cannot perform any checks that appropriate | |
93e790af | 108 | components have been requested. Because of this, the |
a9d69660 NB |
109 | .B Build |
110 | mode should only be used together with a complete understanding of | |
111 | what you are doing. | |
cd29a5c8 NB |
112 | |
113 | .TP | |
114 | .B Create | |
115 | Create a new array with per-device superblocks. | |
116 | '''It can progress | |
117 | '''in several step create-add-add-run or it can all happen with one command. | |
118 | ||
cd29a5c8 NB |
119 | .TP |
120 | .B "Follow or Monitor" | |
5787fa49 | 121 | Monitor one or more md devices and act on any state changes. This is |
93e790af | 122 | only meaningful for raid1, 4, 5, 6, 10 or multipath arrays, as |
98c6faba NB |
123 | only these have interesting state. raid0 or linear never have |
124 | missing, spare, or failed drives, so there is nothing to monitor. | |
5787fa49 | 125 | |
dd0781e5 NB |
126 | .TP |
127 | .B "Grow" | |
128 | Grow (or shrink) an array, or otherwise reshape it in some way. | |
129 | Currently supported growth options including changing the active size | |
93e790af SW |
130 | of component devices and changing the number of active devices in RAID |
131 | levels 1/4/5/6, as well as adding or removing a write-intent bitmap. | |
cd29a5c8 | 132 | |
8382f19b NB |
133 | .TP |
134 | .B "Incremental Assembly" | |
135 | Add a single device to an appropriate array. If the addition of the | |
136 | device makes the array runnable, the array will be started. | |
137 | This provides a convenient interface to a | |
138 | .I hot-plug | |
139 | system. As each device is detected, | |
140 | .I mdadm | |
141 | has a chance to include it in some array as appropriate. | |
142 | ||
2ae555c3 NB |
143 | .TP |
144 | .B Manage | |
145 | This is for doing things to specific components of an array such as | |
146 | adding new spares and removing faulty devices. | |
147 | ||
148 | .TP | |
149 | .B Misc | |
150 | This is an 'everything else' mode that supports operations on active | |
151 | arrays, operations on component devices such as erasing old superblocks, and | |
152 | information gathering operations. | |
153 | '''This mode allows operations on independent devices such as examine MD | |
154 | '''superblocks, erasing old superblocks and stopping active arrays. | |
155 | ||
1f48664b NB |
156 | .TP |
157 | .B Auto-detect | |
158 | This mode does not act on a specific device or array, but rather it | |
159 | requests the Linux Kernel to activate any auto-detected arrays. | |
52826846 NB |
160 | .SH OPTIONS |
161 | ||
2ae555c3 | 162 | .SH Options for selecting a mode are: |
52826846 | 163 | |
cd29a5c8 | 164 | .TP |
7e23fc43 | 165 | .BR \-A ", " \-\-assemble |
2d465520 | 166 | Assemble a pre-existing array. |
52826846 | 167 | |
cd29a5c8 | 168 | .TP |
7e23fc43 | 169 | .BR \-B ", " \-\-build |
cd29a5c8 | 170 | Build a legacy array without superblocks. |
52826846 | 171 | |
cd29a5c8 | 172 | .TP |
7e23fc43 | 173 | .BR \-C ", " \-\-create |
cd29a5c8 | 174 | Create a new array. |
52826846 | 175 | |
cd29a5c8 | 176 | .TP |
7e23fc43 | 177 | .BR \-F ", " \-\-follow ", " \-\-monitor |
cd29a5c8 NB |
178 | Select |
179 | .B Monitor | |
180 | mode. | |
52826846 | 181 | |
dd0781e5 | 182 | .TP |
7e23fc43 | 183 | .BR \-G ", " \-\-grow |
dd0781e5 | 184 | Change the size or shape of an active array. |
8382f19b NB |
185 | |
186 | .TP | |
1f48664b | 187 | .BR \-I ", " \-\-incremental |
8382f19b NB |
188 | Add a single device into an appropriate array, and possibly start the array. |
189 | ||
1f48664b NB |
190 | .TP |
191 | .B \-\-auto-detect | |
192 | Request that the kernel starts any auto-detected arrays. This can only | |
193 | work if | |
194 | .I md | |
195 | is compiled into the kernel \(em not if it is a module. | |
196 | Arrays can be auto-detected by the kernel if all the components are in | |
197 | primary MS-DOS partitions with partition type | |
198 | .BR FD . | |
199 | In-kernel autodetect is not recommended for new installations. Using | |
200 | .I mdadm | |
201 | to detect and assemble arrays \(em possibly in an | |
202 | .I initrd | |
203 | \(em is substantially more flexible and should be preferred. | |
204 | ||
2ae555c3 NB |
205 | .P |
206 | If a device is given before any options, or if the first option is | |
7e23fc43 PS |
207 | .BR \-\-add , |
208 | .BR \-\-fail , | |
2ae555c3 | 209 | or |
7e23fc43 | 210 | .BR \-\-remove , |
2ae555c3 NB |
211 | then the MANAGE mode is assume. |
212 | Anything other than these will cause the | |
213 | .B Misc | |
214 | mode to be assumed. | |
dd0781e5 | 215 | |
2ae555c3 | 216 | .SH Options that are not mode-specific are: |
e793c2e5 | 217 | |
cd29a5c8 | 218 | .TP |
7e23fc43 | 219 | .BR \-h ", " \-\-help |
a9d69660 | 220 | Display general help message or, after one of the above options, a |
93e790af | 221 | mode-specific help message. |
56eedc1a NB |
222 | |
223 | .TP | |
7e23fc43 | 224 | .B \-\-help\-options |
56eedc1a NB |
225 | Display more detailed help about command line parsing and some commonly |
226 | used options. | |
52826846 | 227 | |
cd29a5c8 | 228 | .TP |
7e23fc43 | 229 | .BR \-V ", " \-\-version |
9a9dab36 | 230 | Print version information for mdadm. |
52826846 | 231 | |
cd29a5c8 | 232 | .TP |
7e23fc43 | 233 | .BR \-v ", " \-\-verbose |
22892d56 NB |
234 | Be more verbose about what is happening. This can be used twice to be |
235 | extra-verbose. | |
a9d69660 | 236 | The extra verbosity currently only affects |
7e23fc43 | 237 | .B \-\-detail \-\-scan |
22892d56 | 238 | and |
7e23fc43 | 239 | .BR "\-\-examine \-\-scan" . |
52826846 | 240 | |
dab6685f | 241 | .TP |
7e23fc43 | 242 | .BR \-q ", " \-\-quiet |
dab6685f NB |
243 | Avoid printing purely informative messages. With this, |
244 | .B mdadm | |
245 | will be silent unless there is something really important to report. | |
246 | ||
cd29a5c8 | 247 | .TP |
7e23fc43 | 248 | .BR \-b ", " \-\-brief |
cd29a5c8 | 249 | Be less verbose. This is used with |
7e23fc43 | 250 | .B \-\-detail |
cd29a5c8 | 251 | and |
7e23fc43 | 252 | .BR \-\-examine . |
22892d56 | 253 | Using |
7e23fc43 | 254 | .B \-\-brief |
22892d56 | 255 | with |
7e23fc43 | 256 | .B \-\-verbose |
22892d56 | 257 | gives an intermediate level of verbosity. |
52826846 | 258 | |
e0d19036 | 259 | .TP |
7e23fc43 | 260 | .BR \-f ", " \-\-force |
93e790af | 261 | Be more forceful about certain operations. See the various modes for |
e0d19036 NB |
262 | the exact meaning of this option in different contexts. |
263 | ||
264 | .TP | |
7e23fc43 | 265 | .BR \-c ", " \-\-config= |
2ae555c3 NB |
266 | Specify the config file. Default is to use |
267 | .BR /etc/mdadm.conf , | |
93e790af | 268 | or if that is missing then |
2ae555c3 | 269 | .BR /etc/mdadm/mdadm.conf . |
5787fa49 | 270 | If the config file given is |
93e790af | 271 | .B "partitions" |
5787fa49 NB |
272 | then nothing will be read, but |
273 | .I mdadm | |
274 | will act as though the config file contained exactly | |
275 | .B "DEVICE partitions" | |
276 | and will read | |
277 | .B /proc/partitions | |
278 | to find a list of devices to scan. | |
d013a55e | 279 | If the word |
93e790af | 280 | .B "none" |
d013a55e NB |
281 | is given for the config file, then |
282 | .I mdadm | |
283 | will act as though the config file were empty. | |
e0d19036 NB |
284 | |
285 | .TP | |
7e23fc43 | 286 | .BR \-s ", " \-\-scan |
93e790af | 287 | Scan config file or |
e0d19036 NB |
288 | .B /proc/mdstat |
289 | for missing information. | |
290 | In general, this option gives | |
291 | .B mdadm | |
93e790af SW |
292 | permission to get any missing information (like component devices, |
293 | array devices, array identities, and alert destination) from the | |
294 | configuration file (see previous option); | |
295 | one exception is MISC mode when using | |
7e23fc43 | 296 | .B \-\-detail |
e0d19036 | 297 | or |
93e790af | 298 | .B \-\-stop, |
e0d19036 | 299 | in which case |
7e23fc43 | 300 | .B \-\-scan |
e0d19036 NB |
301 | says to get a list of array devices from |
302 | .BR /proc/mdstat . | |
303 | ||
570c0542 | 304 | .TP |
7e23fc43 | 305 | .B \-e ", " \-\-metadata= |
570c0542 | 306 | Declare the style of superblock (raid metadata) to be used. The |
53e8b987 | 307 | default is 0.90 for |
7e23fc43 | 308 | .BR \-\-create , |
53e8b987 | 309 | and to guess for other operations. |
2790ffe3 GB |
310 | The default can be overridden by setting the |
311 | .B metadata | |
312 | value for the | |
313 | .B CREATE | |
314 | keyword in | |
315 | .BR mdadm.conf . | |
570c0542 NB |
316 | |
317 | Options are: | |
318 | .RS | |
319 | .IP "0, 0.90, default" | |
320 | Use the original 0.90 format superblock. This format limits arrays to | |
93e790af | 321 | 28 component devices and limits component devices of levels 1 and |
570c0542 NB |
322 | greater to 2 terabytes. |
323 | .IP "1, 1.0, 1.1, 1.2" | |
324 | Use the new version-1 format superblock. This has few restrictions. | |
93e790af | 325 | The different sub-versions store the superblock at different locations |
570c0542 NB |
326 | on the device, either at the end (for 1.0), at the start (for 1.1) or |
327 | 4K from the start (for 1.2). | |
328 | .RE | |
329 | ||
41a3b72a | 330 | .TP |
7e23fc43 | 331 | .B \-\-homehost= |
35cc5be4 | 332 | This will override any |
41a3b72a | 333 | .B HOMEHOST |
93e790af | 334 | setting in the config file and provides the identity of the host which |
41a3b72a NB |
335 | should be considered the home for any arrays. |
336 | ||
337 | When creating an array, the | |
338 | .B homehost | |
339 | will be recorded in the superblock. For version-1 superblocks, it will | |
93e790af | 340 | be prefixed to the array name. For version-0.90 superblocks, part of |
41a3b72a NB |
341 | the SHA1 hash of the hostname will be stored in the later half of the |
342 | UUID. | |
343 | ||
344 | When reporting information about an array, any array which is tagged | |
345 | for the given homehost will be reported as such. | |
346 | ||
347 | When using Auto-Assemble, only arrays tagged for the given homehost | |
348 | will be assembled. | |
349 | ||
2ae555c3 NB |
350 | .SH For create, build, or grow: |
351 | ||
352 | .TP | |
7e23fc43 | 353 | .BR \-n ", " \-\-raid\-devices= |
2ae555c3 NB |
354 | Specify the number of active devices in the array. This, plus the |
355 | number of spare devices (see below) must equal the number of | |
356 | .I component-devices | |
357 | (including "\fBmissing\fP" devices) | |
358 | that are listed on the command line for | |
7e23fc43 | 359 | .BR \-\-create . |
2ae555c3 NB |
360 | Setting a value of 1 is probably |
361 | a mistake and so requires that | |
7e23fc43 | 362 | .B \-\-force |
2ae555c3 NB |
363 | be specified first. A value of 1 will then be allowed for linear, |
364 | multipath, raid0 and raid1. It is never allowed for raid4 or raid5. | |
365 | .br | |
366 | This number can only be changed using | |
7e23fc43 | 367 | .B \-\-grow |
00be0b12 NB |
368 | for RAID1, RAID5 and RAID6 arrays, and only on kernels which provide |
369 | necessary support. | |
2ae555c3 NB |
370 | |
371 | .TP | |
7e23fc43 | 372 | .BR \-x ", " \-\-spare\-devices= |
2ae555c3 NB |
373 | Specify the number of spare (eXtra) devices in the initial array. |
374 | Spares can also be added | |
375 | and removed later. The number of component devices listed | |
376 | on the command line must equal the number of raid devices plus the | |
377 | number of spare devices. | |
378 | ||
379 | ||
380 | .TP | |
7e23fc43 | 381 | .BR \-z ", " \-\-size= |
93e790af | 382 | Amount (in Kibibytes) of space to use from each drive in RAID level 1/4/5/6. |
2ae555c3 NB |
383 | This must be a multiple of the chunk size, and must leave about 128Kb |
384 | of space at the end of the drive for the RAID superblock. | |
385 | If this is not specified | |
386 | (as it normally is not) the smallest drive (or partition) sets the | |
387 | size, though if there is a variance among the drives of greater than 1%, a warning is | |
388 | issued. | |
389 | ||
390 | This value can be set with | |
7e23fc43 | 391 | .B \-\-grow |
2ae555c3 NB |
392 | for RAID level 1/4/5/6. If the array was created with a size smaller |
393 | than the currently active drives, the extra space can be accessed | |
394 | using | |
7e23fc43 | 395 | .BR \-\-grow . |
2ae555c3 NB |
396 | The size can be given as |
397 | .B max | |
398 | which means to choose the largest size that fits on all current drives. | |
52826846 | 399 | |
cd29a5c8 | 400 | .TP |
7e23fc43 | 401 | .BR \-c ", " \-\-chunk= |
cd29a5c8 | 402 | Specify chunk size of kibibytes. The default is 64. |
52826846 | 403 | |
cd29a5c8 | 404 | .TP |
7e23fc43 | 405 | .BR \-\-rounding= |
cd29a5c8 | 406 | Specify rounding factor for linear array (==chunk size) |
52826846 | 407 | |
cd29a5c8 | 408 | .TP |
7e23fc43 | 409 | .BR \-l ", " \-\-level= |
aa88f531 | 410 | Set raid level. When used with |
7e23fc43 | 411 | .BR \-\-create , |
98c6faba | 412 | options are: linear, raid0, 0, stripe, raid1, 1, mirror, raid4, 4, |
2ae555c3 | 413 | raid5, 5, raid6, 6, raid10, 10, multipath, mp, faulty. Obviously some of these are synonymous. |
aa88f531 NB |
414 | |
415 | When used with | |
7e23fc43 | 416 | .BR \-\-build , |
a9d69660 | 417 | only linear, stripe, raid0, 0, raid1, multipath, mp, and faulty are valid. |
52826846 | 418 | |
2ae555c3 | 419 | Not yet supported with |
7e23fc43 | 420 | .BR \-\-grow . |
2ae555c3 | 421 | |
cd29a5c8 | 422 | .TP |
7e23fc43 | 423 | .BR \-p ", " \-\-layout= |
1a7dfc35 NB |
424 | This option configures the fine details of data layout for raid5, |
425 | and raid10 arrays, and controls the failure modes for | |
426 | .IR faulty . | |
427 | ||
428 | The layout of the raid5 parity block can be one of | |
7e23fc43 PS |
429 | .BR left\-asymmetric , |
430 | .BR left\-symmetric , | |
431 | .BR right\-asymmetric , | |
432 | .BR right\-symmetric , | |
53e8b987 PS |
433 | .BR la ", " ra ", " ls ", " rs . |
434 | The default is | |
7e23fc43 | 435 | .BR left\-symmetric . |
52826846 | 436 | |
93e790af SW |
437 | When setting the failure mode for level |
438 | .I faulty, | |
1a7dfc35 | 439 | the options are: |
7e23fc43 PS |
440 | .BR write\-transient ", " wt , |
441 | .BR read\-transient ", " rt , | |
442 | .BR write\-persistent ", " wp , | |
443 | .BR read\-persistent ", " rp , | |
444 | .BR write\-all , | |
445 | .BR read\-fixable ", " rf , | |
53e8b987 | 446 | .BR clear ", " flush ", " none . |
b5e64645 | 447 | |
93e790af | 448 | Each failure mode can be followed by a number, which is used as a period |
b5e64645 NB |
449 | between fault generation. Without a number, the fault is generated |
450 | once on the first relevant request. With a number, the fault will be | |
93e790af | 451 | generated after that many requests, and will continue to be generated |
b5e64645 NB |
452 | every time the period elapses. |
453 | ||
454 | Multiple failure modes can be current simultaneously by using the | |
7e23fc43 | 455 | .B \-\-grow |
53e8b987 | 456 | option to set subsequent failure modes. |
b5e64645 NB |
457 | |
458 | "clear" or "none" will remove any pending or periodic failure modes, | |
2ae555c3 | 459 | and "flush" will clear any persistent faults. |
b5e64645 | 460 | |
53e8b987 | 461 | To set the parity with |
7e23fc43 | 462 | .BR \-\-grow , |
53e8b987 | 463 | the level of the array ("faulty") |
b5e64645 NB |
464 | must be specified before the fault mode is specified. |
465 | ||
6f9a21a7 | 466 | Finally, the layout options for RAID10 are one of 'n', 'o' or 'f' followed |
93e790af | 467 | by a small number. The default is 'n2'. The supported options are: |
1a7dfc35 | 468 | |
93e790af | 469 | .I 'n' |
b578481c NB |
470 | signals 'near' copies. Multiple copies of one data block are at |
471 | similar offsets in different devices. | |
472 | ||
93e790af | 473 | .I 'o' |
b578481c NB |
474 | signals 'offset' copies. Rather than the chunks being duplicated |
475 | within a stripe, whole stripes are duplicated but are rotated by one | |
476 | device so duplicate blocks are on different devices. Thus subsequent | |
477 | copies of a block are in the next drive, and are one chunk further | |
478 | down. | |
479 | ||
93e790af | 480 | .I 'f' |
1a7dfc35 | 481 | signals 'far' copies |
93e790af SW |
482 | (multiple copies have very different offsets). |
483 | See md(4) for more detail about 'near' and 'far'. | |
1a7dfc35 NB |
484 | |
485 | The number is the number of copies of each datablock. 2 is normal, 3 | |
486 | can be useful. This number can be at most equal to the number of | |
487 | devices in the array. It does not need to divide evenly into that | |
488 | number (e.g. it is perfectly legal to have an 'n2' layout for an array | |
489 | with an odd number of devices). | |
490 | ||
cd29a5c8 | 491 | .TP |
7e23fc43 | 492 | .BR \-\-parity= |
53e8b987 | 493 | same as |
7e23fc43 | 494 | .B \-\-layout |
53e8b987 | 495 | (thus explaining the p of |
7e23fc43 | 496 | .BR \-p ). |
52826846 | 497 | |
e793c2e5 | 498 | .TP |
7e23fc43 | 499 | .BR \-b ", " \-\-bitmap= |
e793c2e5 | 500 | Specify a file to store a write-intent bitmap in. The file should not |
53e8b987 | 501 | exist unless |
7e23fc43 | 502 | .B \-\-force |
53e8b987 | 503 | is also given. The same file should be provided |
2ae555c3 | 504 | when assembling the array. If the word |
93e790af | 505 | .B "internal" |
2ae555c3 NB |
506 | is given, then the bitmap is stored with the metadata on the array, |
507 | and so is replicated on all devices. If the word | |
93e790af | 508 | .B "none" |
2ae555c3 | 509 | is given with |
7e23fc43 | 510 | .B \-\-grow |
2ae555c3 | 511 | mode, then any bitmap that is present is removed. |
e793c2e5 | 512 | |
2ae555c3 NB |
513 | To help catch typing errors, the filename must contain at least one |
514 | slash ('/') if it is a real file (not 'internal' or 'none'). | |
515 | ||
516 | Note: external bitmaps are only known to work on ext2 and ext3. | |
517 | Storing bitmap files on other filesystems may result in serious problems. | |
e793c2e5 | 518 | |
cd29a5c8 | 519 | .TP |
7e23fc43 | 520 | .BR \-\-bitmap\-chunk= |
2ae555c3 | 521 | Set the chunksize of the bitmap. Each bit corresponds to that many |
1bfdbe01 NB |
522 | Kilobytes of storage. |
523 | When using a file based bitmap, the default is to use the smallest | |
93e790af | 524 | size that is at-least 4 and requires no more than 2^21 chunks. |
2ae555c3 NB |
525 | When using an |
526 | .B internal | |
527 | bitmap, the chunksize is automatically determined to make best use of | |
528 | available space. | |
5787fa49 | 529 | |
cd29a5c8 NB |
530 | |
531 | .TP | |
7e23fc43 | 532 | .BR \-W ", " \-\-write\-mostly |
2ae555c3 | 533 | subsequent devices lists in a |
7e23fc43 PS |
534 | .BR \-\-build , |
535 | .BR \-\-create , | |
2ae555c3 | 536 | or |
7e23fc43 | 537 | .B \-\-add |
2ae555c3 NB |
538 | command will be flagged as 'write-mostly'. This is valid for RAID1 |
539 | only and means that the 'md' driver will avoid reading from these | |
540 | devices if at all possible. This can be useful if mirroring over a | |
541 | slow link. | |
52826846 | 542 | |
2ae555c3 | 543 | .TP |
7e23fc43 | 544 | .BR \-\-write\-behind= |
2ae555c3 NB |
545 | Specify that write-behind mode should be enabled (valid for RAID1 |
546 | only). If an argument is specified, it will set the maximum number | |
547 | of outstanding writes allowed. The default value is 256. | |
548 | A write-intent bitmap is required in order to use write-behind | |
549 | mode, and write-behind is only attempted on drives marked as | |
550 | .IR write-mostly . | |
dd0781e5 NB |
551 | |
552 | .TP | |
7e23fc43 | 553 | .BR \-\-assume\-clean |
dd0781e5 NB |
554 | Tell |
555 | .I mdadm | |
47d79ef8 NB |
556 | that the array pre-existed and is known to be clean. It can be useful |
557 | when trying to recover from a major failure as you can be sure that no | |
558 | data will be affected unless you actually write to the array. It can | |
559 | also be used when creating a RAID1 or RAID10 if you want to avoid the | |
b3f1c093 | 560 | initial resync, however this practice \(em while normally safe \(em is not |
93e790af | 561 | recommended. Use this only if you really know what you are doing. |
dd0781e5 | 562 | |
2ae555c3 | 563 | .TP |
7e23fc43 | 564 | .BR \-\-backup\-file= |
53e8b987 | 565 | This is needed when |
7e23fc43 | 566 | .B \-\-grow |
53e8b987 | 567 | is used to increase the number of |
2ae555c3 NB |
568 | raid-devices in a RAID5 if there are no spare devices available. |
569 | See the section below on RAID_DEVICE CHANGES. The file should be | |
570 | stored on a separate device, not on the raid array being reshaped. | |
571 | ||
947fd4dd | 572 | .TP |
7e23fc43 | 573 | .BR \-N ", " \-\-name= |
947fd4dd NB |
574 | Set a |
575 | .B name | |
576 | for the array. This is currently only effective when creating an | |
577 | array with a version-1 superblock. The name is a simple textual | |
578 | string that can be used to identify array components when assembling. | |
579 | ||
dd0781e5 | 580 | .TP |
7e23fc43 | 581 | .BR \-R ", " \-\-run |
dd0781e5 NB |
582 | Insist that |
583 | .I mdadm | |
584 | run the array, even if some of the components | |
585 | appear to be active in another array or filesystem. Normally | |
586 | .I mdadm | |
587 | will ask for confirmation before including such components in an | |
588 | array. This option causes that question to be suppressed. | |
589 | ||
590 | .TP | |
7e23fc43 | 591 | .BR \-f ", " \-\-force |
dd0781e5 NB |
592 | Insist that |
593 | .I mdadm | |
594 | accept the geometry and layout specified without question. Normally | |
595 | .I mdadm | |
596 | will not allow creation of an array with only one device, and will try | |
597 | to create a raid5 array with one missing drive (as this makes the | |
598 | initial resync work faster). With | |
7e23fc43 | 599 | .BR \-\-force , |
dd0781e5 NB |
600 | .I mdadm |
601 | will not try to be so clever. | |
602 | ||
603 | .TP | |
7e23fc43 | 604 | .BR \-a ", " "\-\-auto{=no,yes,md,mdp,part,p}{NN}" |
48f7b27a NB |
605 | Instruct mdadm to create the device file if needed, possibly allocating |
606 | an unused minor number. "md" causes a non-partitionable array | |
dd0781e5 | 607 | to be used. "mdp", "part" or "p" causes a partitionable array (2.6 and |
2ae555c3 | 608 | later) to be used. "yes" requires the named md device to have |
f9c25f1d | 609 | a 'standard' format, and the type and minor number will be determined |
48f7b27a NB |
610 | from this. See DEVICE NAMES below. |
611 | ||
a9d69660 | 612 | The argument can also come immediately after |
7e23fc43 | 613 | "\-a". e.g. "\-ap". |
dd0781e5 | 614 | |
53e8b987 | 615 | If |
7e23fc43 | 616 | .B \-\-auto |
53e8b987 | 617 | is not given on the command line or in the config file, then |
75723446 | 618 | the default will be |
7e23fc43 | 619 | .BR \-\-auto=yes . |
75723446 | 620 | |
1337546d | 621 | If |
7e23fc43 | 622 | .B \-\-scan |
1337546d NB |
623 | is also given, then any |
624 | .I auto= | |
35cc5be4 | 625 | entries in the config file will override the |
7e23fc43 | 626 | .B \-\-auto |
1337546d NB |
627 | instruction given on the command line. |
628 | ||
dd0781e5 NB |
629 | For partitionable arrays, |
630 | .I mdadm | |
631 | will create the device file for the whole array and for the first 4 | |
632 | partitions. A different number of partitions can be specified at the | |
633 | end of this option (e.g. | |
7e23fc43 | 634 | .BR \-\-auto=p7 ). |
2ae555c3 | 635 | If the device name ends with a digit, the partition names add a 'p', |
48f7b27a | 636 | and a number, e.g. "/dev/home1p3". If there is no |
dd0781e5 NB |
637 | trailing digit, then the partition names just have a number added, |
638 | e.g. "/dev/scratch3". | |
639 | ||
48f7b27a NB |
640 | If the md device name is in a 'standard' format as described in DEVICE |
641 | NAMES, then it will be created, if necessary, with the appropriate | |
642 | number based on that name. If the device name is not in one of these | |
a9d69660 | 643 | formats, then a unused minor number will be allocated. The minor |
48f7b27a NB |
644 | number will be considered unused if there is no active array for that |
645 | number, and there is no entry in /dev for that number and with a | |
646 | non-standard name. | |
647 | ||
38098016 | 648 | .TP |
7e23fc43 | 649 | .BR \-\-symlink = no |
38098016 | 650 | Normally when |
7e23fc43 | 651 | .B \-\-auto |
38098016 NB |
652 | causes |
653 | .I mdadm | |
654 | to create devices in | |
655 | .B /dev/md/ | |
656 | it will also create symlinks from | |
657 | .B /dev/ | |
658 | with names starting with | |
659 | .B md | |
660 | or | |
661 | .BR md_ . | |
662 | Use | |
7e23fc43 | 663 | .B \-\-symlink=no |
38098016 | 664 | to suppress this, or |
7e23fc43 | 665 | .B \-\-symlink=yes |
38098016 NB |
666 | to enforce this even if it is suppressing |
667 | .IR mdadm.conf . | |
668 | ||
669 | ||
52826846 NB |
670 | .SH For assemble: |
671 | ||
cd29a5c8 | 672 | .TP |
7e23fc43 | 673 | .BR \-u ", " \-\-uuid= |
cd29a5c8 NB |
674 | uuid of array to assemble. Devices which don't have this uuid are |
675 | excluded | |
676 | ||
677 | .TP | |
7e23fc43 | 678 | .BR \-m ", " \-\-super\-minor= |
cd29a5c8 NB |
679 | Minor number of device that array was created for. Devices which |
680 | don't have this minor number are excluded. If you create an array as | |
2d465520 | 681 | /dev/md1, then all superblocks will contain the minor number 1, even if |
cd29a5c8 NB |
682 | the array is later assembled as /dev/md2. |
683 | ||
d013a55e | 684 | Giving the literal word "dev" for |
7e23fc43 | 685 | .B \-\-super\-minor |
d013a55e NB |
686 | will cause |
687 | .I mdadm | |
688 | to use the minor number of the md device that is being assembled. | |
689 | e.g. when assembling | |
690 | .BR /dev/md0 , | |
7e23fc43 | 691 | .M \-\-super\-minor=dev |
d013a55e NB |
692 | will look for super blocks with a minor number of 0. |
693 | ||
947fd4dd | 694 | .TP |
7e23fc43 | 695 | .BR \-N ", " \-\-name= |
947fd4dd | 696 | Specify the name of the array to assemble. This must be the name |
624920bb | 697 | that was specified when creating the array. It must either match |
93e790af | 698 | the name stored in the superblock exactly, or it must match |
41a3b72a | 699 | with the current |
624920bb | 700 | .I homehost |
93e790af | 701 | prefixed to the start of the given name. |
947fd4dd | 702 | |
cd29a5c8 | 703 | .TP |
7e23fc43 | 704 | .BR \-f ", " \-\-force |
52826846 NB |
705 | Assemble the array even if some superblocks appear out-of-date |
706 | ||
cd29a5c8 | 707 | .TP |
7e23fc43 | 708 | .BR \-R ", " \-\-run |
b8a8ccf9 NB |
709 | Attempt to start the array even if fewer drives were given than were |
710 | present last time the array was active. Normally if not all the | |
711 | expected drives are found and | |
7e23fc43 | 712 | .B \-\-scan |
cd29a5c8 NB |
713 | is not used, then the array will be assembled but not started. |
714 | With | |
7e23fc43 | 715 | .B \-\-run |
cd29a5c8 | 716 | an attempt will be made to start it anyway. |
52826846 | 717 | |
b8a8ccf9 | 718 | .TP |
7e23fc43 | 719 | .B \-\-no\-degraded |
b8a8ccf9 | 720 | This is the reverse of |
7e23fc43 | 721 | .B \-\-run |
93e790af | 722 | in that it inhibits the startup of array unless all expected drives |
b8a8ccf9 | 723 | are present. This is only needed with |
93e790af SW |
724 | .B \-\-scan, |
725 | and can be used if the physical connections to devices are | |
b8a8ccf9 NB |
726 | not as reliable as you would like. |
727 | ||
dd0781e5 | 728 | .TP |
7e23fc43 | 729 | .BR \-a ", " "\-\-auto{=no,yes,md,mdp,part}" |
dd0781e5 NB |
730 | See this option under Create and Build options. |
731 | ||
e793c2e5 | 732 | .TP |
7e23fc43 | 733 | .BR \-b ", " \-\-bitmap= |
2ae555c3 NB |
734 | Specify the bitmap file that was given when the array was created. If |
735 | an array has an | |
736 | .B internal | |
737 | bitmap, there is no need to specify this when assembling the array. | |
738 | ||
739 | .TP | |
7e23fc43 | 740 | .BR \-\-backup\-file= |
2ae555c3 | 741 | If |
7e23fc43 | 742 | .B \-\-backup\-file |
2ae555c3 NB |
743 | was used to grow the number of raid-devices in a RAID5, and the system |
744 | crashed during the critical section, then the same | |
7e23fc43 | 745 | .B \-\-backup\-file |
53e8b987 | 746 | must be presented to |
7e23fc43 | 747 | .B \-\-assemble |
53e8b987 | 748 | to allow possibly corrupted data to be restored. |
e793c2e5 | 749 | |
5787fa49 | 750 | .TP |
7e23fc43 | 751 | .BR \-U ", " \-\-update= |
5787fa49 | 752 | Update the superblock on each device while assembling the array. The |
feb716e9 NB |
753 | argument given to this flag can be one of |
754 | .BR sparc2.2 , | |
755 | .BR summaries , | |
7d99579f | 756 | .BR uuid , |
c4f12c13 | 757 | .BR name , |
0237e0ca | 758 | .BR homehost , |
e5329c37 | 759 | .BR resync , |
586ed405 | 760 | .BR byteorder , |
bee8ec56 | 761 | .BR devicesize , |
5787fa49 | 762 | or |
7e23fc43 | 763 | .BR super\-minor . |
5787fa49 NB |
764 | |
765 | The | |
766 | .B sparc2.2 | |
7d99579f | 767 | option will adjust the superblock of an array what was created on a Sparc |
5787fa49 NB |
768 | machine running a patched 2.2 Linux kernel. This kernel got the |
769 | alignment of part of the superblock wrong. You can use the | |
7e23fc43 | 770 | .B "\-\-examine \-\-sparc2.2" |
5787fa49 NB |
771 | option to |
772 | .I mdadm | |
773 | to see what effect this would have. | |
774 | ||
775 | The | |
7e23fc43 | 776 | .B super\-minor |
5787fa49 | 777 | option will update the |
2ae555c3 | 778 | .B "preferred minor" |
5787fa49 | 779 | field on each superblock to match the minor number of the array being |
45c073c9 NB |
780 | assembled. |
781 | This can be useful if | |
7e23fc43 | 782 | .B \-\-examine |
45c073c9 | 783 | reports a different "Preferred Minor" to |
7e23fc43 | 784 | .BR \-\-detail . |
45c073c9 NB |
785 | In some cases this update will be performed automatically |
786 | by the kernel driver. In particular the update happens automatically | |
787 | at the first write to an array with redundancy (RAID level 1 or | |
788 | greater) on a 2.6 (or later) kernel. | |
5787fa49 | 789 | |
7d99579f NB |
790 | The |
791 | .B uuid | |
792 | option will change the uuid of the array. If a UUID is given with the | |
7e23fc43 | 793 | .B \-\-uuid |
53e8b987 | 794 | option that UUID will be used as a new UUID and will |
7d99579f NB |
795 | .B NOT |
796 | be used to help identify the devices in the array. | |
53e8b987 | 797 | If no |
7e23fc43 | 798 | .B \-\-uuid |
53e8b987 | 799 | is given, a random UUID is chosen. |
7d99579f | 800 | |
c4f12c13 NB |
801 | The |
802 | .B name | |
803 | option will change the | |
804 | .I name | |
805 | of the array as stored in the superblock. This is only supported for | |
806 | version-1 superblocks. | |
807 | ||
0237e0ca NB |
808 | The |
809 | .B homehost | |
810 | option will change the | |
811 | .I homehost | |
812 | as recorded in the superblock. For version-0 superblocks, this is the | |
813 | same as updating the UUID. | |
814 | For version-1 superblocks, this involves updating the name. | |
815 | ||
e5329c37 NB |
816 | The |
817 | .B resync | |
818 | option will cause the array to be marked | |
819 | .I dirty | |
820 | meaning that any redundancy in the array (e.g. parity for raid5, | |
821 | copies for raid1) may be incorrect. This will cause the raid system | |
822 | to perform a "resync" pass to make sure that all redundant information | |
823 | is correct. | |
824 | ||
586ed405 NB |
825 | The |
826 | .B byteorder | |
827 | option allows arrays to be moved between machines with different | |
828 | byte-order. | |
2ae555c3 | 829 | When assembling such an array for the first time after a move, giving |
7e23fc43 | 830 | .B "\-\-update=byteorder" |
586ed405 NB |
831 | will cause |
832 | .I mdadm | |
833 | to expect superblocks to have their byteorder reversed, and will | |
834 | correct that order before assembling the array. This is only valid | |
2ae555c3 | 835 | with original (Version 0.90) superblocks. |
586ed405 | 836 | |
feb716e9 NB |
837 | The |
838 | .B summaries | |
839 | option will correct the summaries in the superblock. That is the | |
840 | counts of total, working, active, failed, and spare devices. | |
5787fa49 | 841 | |
bee8ec56 NB |
842 | The |
843 | .B devicesize | |
844 | will rarely be of use. It applies to version 1.1 and 1.2 metadata | |
845 | only (where the metadata is at the start of the device) and is only | |
846 | useful when the component device has changed size (typically become | |
847 | larger). The version 1 metadata records the amount of the device that | |
848 | can be used to store data, so if a device in a version 1.1 or 1.2 | |
849 | array becomes larger, the metadata will still be visible, but the | |
850 | extra space will not. In this case it might be useful to assemble the | |
851 | array with | |
7e23fc43 | 852 | .BR \-\-update=devicesize . |
bee8ec56 NB |
853 | This will cause |
854 | .I mdadm | |
855 | to determine the maximum usable amount of space on each device and | |
856 | update the relevant field in the metadata. | |
857 | ||
41a3b72a | 858 | .TP |
7e23fc43 | 859 | .B \-\-auto\-update\-homehost |
93e790af | 860 | This flag is only meaningful with auto-assembly (see discussion below). |
41a3b72a NB |
861 | In that situation, if no suitable arrays are found for this homehost, |
862 | .I mdadm | |
93e790af | 863 | will rescan for any arrays at all and will assemble them and update the |
41a3b72a NB |
864 | homehost to match the current host. |
865 | ||
e0d19036 | 866 | .SH For Manage mode: |
52826846 | 867 | |
cd29a5c8 | 868 | .TP |
7e23fc43 | 869 | .BR \-a ", " \-\-add |
2ae555c3 | 870 | hot-add listed devices. |
52826846 | 871 | |
fe80f49b | 872 | .TP |
7e23fc43 | 873 | .BR \-\-re\-add |
2ae555c3 | 874 | re-add a device that was recently removed from an array. |
fe80f49b | 875 | |
cd29a5c8 | 876 | .TP |
7e23fc43 | 877 | .BR \-r ", " \-\-remove |
2d465520 | 878 | remove listed devices. They must not be active. i.e. they should |
b80da661 NB |
879 | be failed or spare devices. As well as the name of a device file |
880 | (e.g. | |
881 | .BR /dev/sda1 ) | |
882 | the words | |
883 | .B failed | |
884 | and | |
885 | .B detached | |
886 | can be given to | |
887 | .BR \-\-remove . | |
888 | The first causes all failed device to be removed. The second causes | |
93e790af | 889 | any device which is no longer connected to the system (i.e an 'open' |
b80da661 NB |
890 | returns |
891 | .BR ENXIO ) | |
892 | to be removed. This will only succeed for devices that are spares or | |
893 | have already been marked as failed. | |
52826846 | 894 | |
cd29a5c8 | 895 | .TP |
7e23fc43 | 896 | .BR \-f ", " \-\-fail |
cd29a5c8 | 897 | mark listed devices as faulty. |
b80da661 NB |
898 | As well as the name of a device file, the word |
899 | .B detached | |
900 | can be given. This will cause any device that has been detached from | |
901 | the system to be marked as failed. It can then be removed. | |
52826846 | 902 | |
cd29a5c8 | 903 | .TP |
7e23fc43 | 904 | .BR \-\-set\-faulty |
53e8b987 | 905 | same as |
7e23fc43 | 906 | .BR \-\-fail . |
52826846 | 907 | |
2ae555c3 | 908 | .P |
93e790af SW |
909 | Each of these options require that the first device listed is the array |
910 | to be acted upon, and the remainder are component devices to be added, | |
911 | removed, or marked as faulty. Several different operations can be | |
2ae555c3 NB |
912 | specified for different devices, e.g. |
913 | .in +5 | |
7e23fc43 | 914 | mdadm /dev/md0 \-\-add /dev/sda1 \-\-fail /dev/sdb1 \-\-remove /dev/sdb1 |
2ae555c3 NB |
915 | .in -5 |
916 | Each operation applies to all devices listed until the next | |
93e790af | 917 | operation. |
2ae555c3 NB |
918 | |
919 | If an array is using a write-intent bitmap, then devices which have | |
920 | been removed can be re-added in a way that avoids a full | |
93e790af | 921 | reconstruction but instead just updates the blocks that have changed |
2ae555c3 NB |
922 | since the device was removed. For arrays with persistent metadata |
923 | (superblocks) this is done automatically. For arrays created with | |
7e23fc43 | 924 | .B \-\-build |
2ae555c3 | 925 | mdadm needs to be told that this device we removed recently with |
7e23fc43 | 926 | .BR \-\-re\-add . |
2ae555c3 NB |
927 | |
928 | Devices can only be removed from an array if they are not in active | |
93e790af SW |
929 | use, i.e. that must be spares or failed devices. To remove an active |
930 | device, it must first be marked as | |
931 | .B faulty. | |
2ae555c3 NB |
932 | |
933 | .SH For Misc mode: | |
934 | ||
935 | .TP | |
7e23fc43 | 936 | .BR \-Q ", " \-\-query |
2ae555c3 NB |
937 | Examine a device to see |
938 | (1) if it is an md device and (2) if it is a component of an md | |
939 | array. | |
940 | Information about what is discovered is presented. | |
941 | ||
942 | .TP | |
7e23fc43 | 943 | .BR \-D ", " \-\-detail |
2ae555c3 | 944 | Print detail of one or more md devices. |
5787fa49 | 945 | |
54bad364 KS |
946 | .TP |
947 | .BR \-Y ", " \-\-export | |
948 | When used with | |
949 | .BR \-\-detail , | |
950 | output will be formatted as | |
951 | .B key=value | |
952 | pairs for easy import into the environment. | |
953 | ||
2ae555c3 | 954 | .TP |
7e23fc43 | 955 | .BR \-E ", " \-\-examine |
2ae555c3 | 956 | Print content of md superblock on device(s). |
5787fa49 | 957 | .TP |
7e23fc43 | 958 | .B \-\-sparc2.2 |
a9d69660 | 959 | If an array was created on a 2.2 Linux kernel patched with RAID |
5787fa49 NB |
960 | support, the superblock will have been created incorrectly, or at |
961 | least incompatibly with 2.4 and later kernels. Using the | |
7e23fc43 | 962 | .B \-\-sparc2.2 |
5787fa49 | 963 | flag with |
7e23fc43 | 964 | .B \-\-examine |
5787fa49 NB |
965 | will fix the superblock before displaying it. If this appears to do |
966 | the right thing, then the array can be successfully assembled using | |
7e23fc43 | 967 | .BR "\-\-assemble \-\-update=sparc2.2" . |
5787fa49 | 968 | |
2ae555c3 | 969 | .TP |
7e23fc43 | 970 | .BR \-X ", " \-\-examine\-bitmap |
2ae555c3 | 971 | Report information about a bitmap file. |
01d9299c NB |
972 | The argument is either an external bitmap file or an array component |
973 | in case of an internal bitmap. | |
e0d19036 | 974 | |
cd29a5c8 | 975 | .TP |
7e23fc43 | 976 | .BR \-R ", " \-\-run |
cd29a5c8 | 977 | start a partially built array. |
52826846 | 978 | |
cd29a5c8 | 979 | .TP |
7e23fc43 | 980 | .BR \-S ", " \-\-stop |
cd29a5c8 | 981 | deactivate array, releasing all resources. |
52826846 | 982 | |
cd29a5c8 | 983 | .TP |
7e23fc43 | 984 | .BR \-o ", " \-\-readonly |
cd29a5c8 | 985 | mark array as readonly. |
52826846 | 986 | |
cd29a5c8 | 987 | .TP |
7e23fc43 | 988 | .BR \-w ", " \-\-readwrite |
cd29a5c8 | 989 | mark array as readwrite. |
52826846 | 990 | |
e0d19036 | 991 | .TP |
7e23fc43 | 992 | .B \-\-zero\-superblock |
e0d19036 | 993 | If the device contains a valid md superblock, the block is |
35cc5be4 | 994 | overwritten with zeros. With |
7e23fc43 | 995 | .B \-\-force |
35cc5be4 | 996 | the block where the superblock would be is overwritten even if it |
e0d19036 | 997 | doesn't appear to be valid. |
52826846 | 998 | |
feb716e9 | 999 | .TP |
7e23fc43 | 1000 | .BR \-t ", " \-\-test |
feb716e9 | 1001 | When used with |
7e23fc43 | 1002 | .BR \-\-detail , |
feb716e9 NB |
1003 | the exit status of |
1004 | .I mdadm | |
1005 | is set to reflect the status of the device. | |
1006 | ||
b90c0e9a | 1007 | .TP |
7e23fc43 | 1008 | .BR \-W ", " \-\-wait |
b90c0e9a NB |
1009 | For each md device given, wait for any resync, recovery, or reshape |
1010 | activity to finish before returning. | |
1011 | .I mdadm | |
1012 | will return with success if it actually waited for every device | |
1013 | listed, otherwise it will return failure. | |
1014 | ||
8382f19b NB |
1015 | .SH For Incremental Assembly mode: |
1016 | .TP | |
7e23fc43 | 1017 | .BR \-\-rebuild\-map ", " \-r |
8382f19b NB |
1018 | Rebuild the map file |
1019 | .RB ( /var/run/mdadm/map ) | |
1020 | that | |
1021 | .I mdadm | |
1022 | uses to help track which arrays are currently being assembled. | |
1023 | ||
1024 | .TP | |
7e23fc43 | 1025 | .BR \-\-run ", " \-R |
8382f19b NB |
1026 | Run any array assembled as soon as a minimal number of devices are |
1027 | available, rather than waiting until all expected devices are present. | |
1028 | ||
1029 | .TP | |
7e23fc43 | 1030 | .BR \-\-scan ", " \-s |
8382f19b | 1031 | Only meaningful with |
7e23fc43 | 1032 | .B \-R |
8382f19b NB |
1033 | this will scan the |
1034 | .B map | |
1035 | file for arrays that are being incrementally assembled and will try to | |
1036 | start any that are not already started. If any such array is listed | |
1037 | in | |
1038 | .B mdadm.conf | |
1039 | as requiring an external bitmap, that bitmap will be attached first. | |
1040 | ||
e0d19036 NB |
1041 | .SH For Monitor mode: |
1042 | .TP | |
7e23fc43 | 1043 | .BR \-m ", " \-\-mail |
e0d19036 NB |
1044 | Give a mail address to send alerts to. |
1045 | ||
1046 | .TP | |
7e23fc43 | 1047 | .BR \-p ", " \-\-program ", " \-\-alert |
e0d19036 NB |
1048 | Give a program to be run whenever an event is detected. |
1049 | ||
773135f5 | 1050 | .TP |
7e23fc43 | 1051 | .BR \-y ", " \-\-syslog |
773135f5 NB |
1052 | Cause all events to be reported through 'syslog'. The messages have |
1053 | facility of 'daemon' and varying priorities. | |
1054 | ||
e0d19036 | 1055 | .TP |
7e23fc43 | 1056 | .BR \-d ", " \-\-delay |
e0d19036 NB |
1057 | Give a delay in seconds. |
1058 | .B mdadm | |
1059 | polls the md arrays and then waits this many seconds before polling | |
1060 | again. The default is 60 seconds. | |
1061 | ||
d013a55e | 1062 | .TP |
7e23fc43 | 1063 | .BR \-f ", " \-\-daemonise |
d013a55e NB |
1064 | Tell |
1065 | .B mdadm | |
1066 | to run as a background daemon if it decides to monitor anything. This | |
1067 | causes it to fork and run in the child, and to disconnect form the | |
1068 | terminal. The process id of the child is written to stdout. | |
1069 | This is useful with | |
7e23fc43 | 1070 | .B \-\-scan |
d013a55e NB |
1071 | which will only continue monitoring if a mail address or alert program |
1072 | is found in the config file. | |
1073 | ||
b5e64645 | 1074 | .TP |
7e23fc43 | 1075 | .BR \-i ", " \-\-pid\-file |
b5e64645 NB |
1076 | When |
1077 | .B mdadm | |
1078 | is running in daemon mode, write the pid of the daemon process to | |
1079 | the specified file, instead of printing it on standard output. | |
1080 | ||
aa88f531 | 1081 | .TP |
7e23fc43 | 1082 | .BR \-1 ", " \-\-oneshot |
aa88f531 NB |
1083 | Check arrays only once. This will generate |
1084 | .B NewArray | |
1085 | events and more significantly | |
1086 | .B DegradedArray | |
a9d69660 NB |
1087 | and |
1088 | .B SparesMissing | |
aa88f531 NB |
1089 | events. Running |
1090 | .in +5 | |
7e23fc43 | 1091 | .B " mdadm \-\-monitor \-\-scan \-1" |
aa88f531 NB |
1092 | .in -5 |
1093 | from a cron script will ensure regular notification of any degraded arrays. | |
1094 | ||
98c6faba | 1095 | .TP |
7e23fc43 | 1096 | .BR \-t ", " \-\-test |
98c6faba NB |
1097 | Generate a |
1098 | .B TestMessage | |
1099 | alert for every array found at startup. This alert gets mailed and | |
1100 | passed to the alert program. This can be used for testing that alert | |
a9d69660 | 1101 | message do get through successfully. |
98c6faba | 1102 | |
e0d19036 | 1103 | .SH ASSEMBLE MODE |
52826846 | 1104 | |
cd29a5c8 NB |
1105 | .HP 12 |
1106 | Usage: | |
7e23fc43 | 1107 | .B mdadm \-\-assemble |
5787fa49 NB |
1108 | .I md-device options-and-component-devices... |
1109 | .HP 12 | |
1110 | Usage: | |
7e23fc43 | 1111 | .B mdadm \-\-assemble \-\-scan |
5787fa49 | 1112 | .I md-devices-and-options... |
cd29a5c8 NB |
1113 | .HP 12 |
1114 | Usage: | |
7e23fc43 | 1115 | .B mdadm \-\-assemble \-\-scan |
cd29a5c8 | 1116 | .I options... |
52826846 | 1117 | |
cd29a5c8 | 1118 | .PP |
52826846 | 1119 | This usage assembles one or more raid arrays from pre-existing components. |
9a9dab36 | 1120 | For each array, mdadm needs to know the md device, the identity of the |
e0d19036 | 1121 | array, and a number of component-devices. These can be found in a number of ways. |
52826846 | 1122 | |
5787fa49 | 1123 | In the first usage example (without the |
7e23fc43 | 1124 | .BR \-\-scan ) |
5787fa49 NB |
1125 | the first device given is the md device. |
1126 | In the second usage example, all devices listed are treated as md | |
1127 | devices and assembly is attempted. | |
1128 | In the third (where no devices are listed) all md devices that are | |
1129 | listed in the configuration file are assembled. | |
52826846 | 1130 | |
d013a55e | 1131 | If precisely one device is listed, but |
7e23fc43 | 1132 | .B \-\-scan |
dd0781e5 | 1133 | is not given, then |
d013a55e NB |
1134 | .I mdadm |
1135 | acts as though | |
7e23fc43 | 1136 | .B \-\-scan |
93e790af | 1137 | was given and identity information is extracted from the configuration file. |
d013a55e | 1138 | |
2ae555c3 | 1139 | The identity can be given with the |
7e23fc43 | 1140 | .B \-\-uuid |
cd29a5c8 | 1141 | option, with the |
7e23fc43 | 1142 | .B \-\-super\-minor |
93e790af SW |
1143 | option, will be taken from the md-device record in the config file, or |
1144 | will be taken from the super block of the first component-device | |
1145 | listed on the command line. | |
52826846 | 1146 | |
2ae555c3 | 1147 | Devices can be given on the |
7e23fc43 | 1148 | .B \-\-assemble |
5787fa49 NB |
1149 | command line or in the config file. Only devices which have an md |
1150 | superblock which contains the right identity will be considered for | |
1151 | any array. | |
52826846 | 1152 | |
2ae555c3 | 1153 | The config file is only used if explicitly named with |
7e23fc43 | 1154 | .B \-\-config |
d013a55e | 1155 | or requested with (a possibly implicit) |
7e23fc43 | 1156 | .BR \-\-scan . |
52826846 | 1157 | In the later case, |
9a9dab36 | 1158 | .B /etc/mdadm.conf |
52826846 NB |
1159 | is used. |
1160 | ||
2ae555c3 | 1161 | If |
7e23fc43 | 1162 | .B \-\-scan |
cd29a5c8 NB |
1163 | is not given, then the config file will only be used to find the |
1164 | identity of md arrays. | |
52826846 | 1165 | |
2d465520 | 1166 | Normally the array will be started after it is assembled. However if |
7e23fc43 | 1167 | .B \-\-scan |
2d465520 | 1168 | is not given and insufficient drives were listed to start a complete |
cd29a5c8 NB |
1169 | (non-degraded) array, then the array is not started (to guard against |
1170 | usage errors). To insist that the array be started in this case (as | |
1a7dfc35 | 1171 | may work for RAID1, 4, 5, 6, or 10), give the |
7e23fc43 | 1172 | .B \-\-run |
cd29a5c8 | 1173 | flag. |
52826846 | 1174 | |
75723446 NB |
1175 | If the md device does not exist, then it will be created providing the |
1176 | intent is clear. i.e. the name must be in a standard form, or the | |
7e23fc43 | 1177 | .B \-\-auto |
75723446 NB |
1178 | option must be given to clarify how and whether the device should be |
1179 | created. | |
dd0781e5 | 1180 | This can be useful for handling partitioned devices (which don't have |
b3f1c093 | 1181 | a stable device number \(em it can change after a reboot) and when using |
dd0781e5 NB |
1182 | "udev" to manage your |
1183 | .B /dev | |
1184 | tree (udev cannot handle md devices because of the unusual device | |
1185 | initialisation conventions). | |
1186 | ||
1187 | If the option to "auto" is "mdp" or "part" or (on the command line | |
1188 | only) "p", then mdadm will create a partitionable array, using the | |
93e790af | 1189 | first free one that is not in use and does not already have an entry |
dd0781e5 NB |
1190 | in /dev (apart from numeric /dev/md* entries). |
1191 | ||
1192 | If the option to "auto" is "yes" or "md" or (on the command line) | |
1193 | nothing, then mdadm will create a traditional, non-partitionable md | |
1194 | array. | |
1195 | ||
1196 | It is expected that the "auto" functionality will be used to create | |
1197 | device entries with meaningful names such as "/dev/md/home" or | |
1198 | "/dev/md/root", rather than names based on the numerical array number. | |
1199 | ||
93e790af | 1200 | When using option "auto" to create a partitionable array, the device |
dd0781e5 NB |
1201 | files for the first 4 partitions are also created. If a different |
1202 | number is required it can be simply appended to the auto option. | |
1203 | e.g. "auto=part8". Partition names are created by appending a digit | |
a9d69660 | 1204 | string to the device name, with an intervening "p" if the device name |
dd0781e5 NB |
1205 | ends with a digit. |
1206 | ||
1207 | The | |
7e23fc43 | 1208 | .B \-\-auto |
dd0781e5 NB |
1209 | option is also available in Build and Create modes. As those modes do |
1210 | not use a config file, the "auto=" config option does not apply to | |
1211 | these modes. | |
52826846 | 1212 | |
41a3b72a NB |
1213 | .SS Auto Assembly |
1214 | When | |
7e23fc43 | 1215 | .B \-\-assemble |
41a3b72a | 1216 | is used with |
7e23fc43 | 1217 | .B \-\-scan |
41a3b72a NB |
1218 | and no devices are listed, |
1219 | .I mdadm | |
1220 | will first attempt to assemble all the arrays listed in the config | |
1221 | file. | |
1222 | ||
1223 | If a | |
1224 | .B homehost | |
1225 | has been specified (either in the config file or on the command line), | |
1226 | .I mdadm | |
1227 | will look further for possible arrays and will try to assemble | |
1228 | anything that it finds which is tagged as belonging to the given | |
1229 | homehost. This is the only situation where | |
1230 | .I mdadm | |
1231 | will assemble arrays without being given specific device name or | |
93e790af | 1232 | identity information for the array. |
41a3b72a NB |
1233 | |
1234 | If | |
1235 | .I mdadm | |
1236 | finds a consistent set of devices that look like they should comprise | |
1237 | an array, and if the superblock is tagged as belonging to the given | |
1238 | home host, it will automatically choose a device name and try to | |
1239 | assemble the array. If the array uses version-0.90 metadata, then the | |
1240 | .B minor | |
1241 | number as recorded in the superblock is used to create a name in | |
1242 | .B /dev/md/ | |
1243 | so for example | |
1244 | .BR /dev/md/3 . | |
1245 | If the array uses version-1 metadata, then the | |
1246 | .B name | |
1247 | from the superblock is used to similarly create a name in | |
93e790af SW |
1248 | .BR /dev/md |
1249 | (the name will have any 'host' prefix stripped first). | |
41a3b72a NB |
1250 | |
1251 | If | |
1252 | .I mdadm | |
1253 | cannot find any array for the given host at all, and if | |
7e23fc43 | 1254 | .B \-\-auto\-update\-homehost |
41a3b72a NB |
1255 | is given, then |
1256 | .I mdadm | |
1257 | will search again for any array (not just an array created for this | |
1258 | host) and will assemble each assuming | |
7e23fc43 | 1259 | .BR \-\-update=homehost . |
41a3b72a NB |
1260 | This will change the host tag in the superblock so that on the next run, |
1261 | these arrays will be found without the second pass. The intention of | |
1262 | this feature is to support transitioning a set of md arrays to using | |
1263 | homehost tagging. | |
1264 | ||
1265 | The reason for requiring arrays to be tagged with the homehost for | |
1266 | auto assembly is to guard against problems that can arise when moving | |
1267 | devices from one host to another. | |
1268 | ||
cd29a5c8 | 1269 | .SH BUILD MODE |
52826846 | 1270 | |
cd29a5c8 NB |
1271 | .HP 12 |
1272 | Usage: | |
7e23fc43 | 1273 | .B mdadm \-\-build |
93e790af | 1274 | .I md-device |
7e23fc43 PS |
1275 | .BI \-\-chunk= X |
1276 | .BI \-\-level= Y | |
1277 | .BI \-\-raid\-devices= Z | |
cd29a5c8 NB |
1278 | .I devices |
1279 | ||
1280 | .PP | |
2ae555c3 | 1281 | This usage is similar to |
7e23fc43 | 1282 | .BR \-\-create . |
a9d69660 | 1283 | The difference is that it creates an array without a superblock. With |
cd29a5c8 | 1284 | these arrays there is no difference between initially creating the array and |
52826846 NB |
1285 | subsequently assembling the array, except that hopefully there is useful |
1286 | data there in the second case. | |
1287 | ||
a9d69660 NB |
1288 | The level may raid0, linear, multipath, or faulty, or one of their |
1289 | synonyms. All devices must be listed and the array will be started | |
1290 | once complete. | |
cd29a5c8 NB |
1291 | |
1292 | .SH CREATE MODE | |
1293 | ||
1294 | .HP 12 | |
1295 | Usage: | |
7e23fc43 | 1296 | .B mdadm \-\-create |
93e790af | 1297 | .I md-device |
7e23fc43 PS |
1298 | .BI \-\-chunk= X |
1299 | .BI \-\-level= Y | |
cd29a5c8 | 1300 | .br |
7e23fc43 | 1301 | .BI \-\-raid\-devices= Z |
cd29a5c8 NB |
1302 | .I devices |
1303 | ||
1304 | .PP | |
1305 | This usage will initialise a new md array, associate some devices with | |
1306 | it, and activate the array. | |
1307 | ||
a9d69660 | 1308 | If the |
7e23fc43 | 1309 | .B \-\-auto |
dd0781e5 NB |
1310 | option is given (as described in more detail in the section on |
1311 | Assemble mode), then the md device will be created with a suitable | |
1312 | device number if necessary. | |
1313 | ||
cd29a5c8 | 1314 | As devices are added, they are checked to see if they contain raid |
2d465520 | 1315 | superblocks or filesystems. They are also checked to see if the variance in |
cd29a5c8 NB |
1316 | device size exceeds 1%. |
1317 | ||
1318 | If any discrepancy is found, the array will not automatically be run, though | |
2ae555c3 | 1319 | the presence of a |
7e23fc43 | 1320 | .B \-\-run |
cd29a5c8 NB |
1321 | can override this caution. |
1322 | ||
2d465520 | 1323 | To create a "degraded" array in which some devices are missing, simply |
d013a55e | 1324 | give the word "\fBmissing\fP" |
2d465520 NB |
1325 | in place of a device name. This will cause |
1326 | .B mdadm | |
1327 | to leave the corresponding slot in the array empty. | |
1328 | For a RAID4 or RAID5 array at most one slot can be | |
98c6faba | 1329 | "\fBmissing\fP"; for a RAID6 array at most two slots. |
2d465520 NB |
1330 | For a RAID1 array, only one real device needs to be given. All of the |
1331 | others can be | |
d013a55e | 1332 | "\fBmissing\fP". |
2d465520 | 1333 | |
feb716e9 NB |
1334 | When creating a RAID5 array, |
1335 | .B mdadm | |
1336 | will automatically create a degraded array with an extra spare drive. | |
1337 | This is because building the spare into a degraded array is in general faster than resyncing | |
1338 | the parity on a non-degraded, but not clean, array. This feature can | |
35cc5be4 | 1339 | be overridden with the |
7e23fc43 | 1340 | .B \-\-force |
feb716e9 NB |
1341 | option. |
1342 | ||
41a3b72a NB |
1343 | When creating an array with version-1 metadata a name for the host is |
1344 | required. | |
1345 | If this is not given with the | |
7e23fc43 | 1346 | .B \-\-name |
41a3b72a NB |
1347 | option, |
1348 | .I mdadm | |
1349 | will chose a name based on the last component of the name of the | |
1350 | device being created. So if | |
1351 | .B /dev/md3 | |
1352 | is being created, then the name | |
1353 | .B 3 | |
1354 | will be chosen. | |
1355 | If | |
1356 | .B /dev/md/home | |
1357 | is being created, then the name | |
1358 | .B home | |
1359 | will be used. | |
1360 | ||
3d3dd91e NB |
1361 | A new array will normally get a randomly assigned 128bit UUID which is |
1362 | very likely to be unique. If you have a specific need, you can choose | |
1363 | a UUID for the array by giving the | |
7e23fc43 | 1364 | .B \-\-uuid= |
3d3dd91e NB |
1365 | option. Be warned that creating two arrays with the same UUID is a |
1366 | recipe for disaster. Also, using | |
7e23fc43 | 1367 | .B \-\-uuid= |
3d3dd91e | 1368 | when creating a v0.90 array will silently override any |
7e23fc43 | 1369 | .B \-\-homehost= |
3d3dd91e | 1370 | setting. |
2ae555c3 | 1371 | '''If the |
7e23fc43 | 1372 | '''.B \-\-size |
e0d19036 | 1373 | '''option is given, it is not necessary to list any component-devices in this command. |
cd29a5c8 | 1374 | '''They can be added later, before a |
7e23fc43 | 1375 | '''.B \-\-run. |
2ae555c3 | 1376 | '''If no |
7e23fc43 | 1377 | '''.B \-\-size |
cd29a5c8 NB |
1378 | '''is given, the apparent size of the smallest drive given is used. |
1379 | ||
53e8b987 | 1380 | The General Management options that are valid with |
7e23fc43 | 1381 | .B \-\-create |
53e8b987 | 1382 | are: |
cd29a5c8 | 1383 | .TP |
7e23fc43 | 1384 | .B \-\-run |
dd0781e5 | 1385 | insist on running the array even if some devices look like they might |
cd29a5c8 NB |
1386 | be in use. |
1387 | ||
1388 | .TP | |
7e23fc43 | 1389 | .B \-\-readonly |
b3f1c093 | 1390 | start the array readonly \(em not supported yet. |
52826846 | 1391 | |
2ae555c3 | 1392 | |
e0d19036 | 1393 | .SH MANAGE MODE |
cd29a5c8 NB |
1394 | .HP 12 |
1395 | Usage: | |
e0d19036 NB |
1396 | .B mdadm |
1397 | .I device | |
1398 | .I options... devices... | |
cd29a5c8 NB |
1399 | .PP |
1400 | ||
e0d19036 NB |
1401 | This usage will allow individual devices in an array to be failed, |
1402 | removed or added. It is possible to perform multiple operations with | |
1403 | on command. For example: | |
1404 | .br | |
7e23fc43 | 1405 | .B " mdadm /dev/md0 \-f /dev/hda1 \-r /dev/hda1 \-a /dev/hda1" |
e0d19036 NB |
1406 | .br |
1407 | will firstly mark | |
1408 | .B /dev/hda1 | |
1409 | as faulty in | |
1410 | .B /dev/md0 | |
1411 | and will then remove it from the array and finally add it back | |
2d465520 | 1412 | in as a spare. However only one md array can be affected by a single |
2ae555c3 | 1413 | command. |
e0d19036 NB |
1414 | |
1415 | .SH MISC MODE | |
1416 | .HP 12 | |
1417 | Usage: | |
9a9dab36 | 1418 | .B mdadm |
e0d19036 NB |
1419 | .I options ... |
1420 | .I devices ... | |
1421 | .PP | |
cd29a5c8 | 1422 | |
b5e64645 | 1423 | MISC mode includes a number of distinct operations that |
e0d19036 NB |
1424 | operate on distinct devices. The operations are: |
1425 | .TP | |
962a108f | 1426 | .B \-\-query |
e0d19036 NB |
1427 | The device is examined to see if it is |
1428 | (1) an active md array, or | |
1429 | (2) a component of an md array. | |
1430 | The information discovered is reported. | |
1431 | ||
1432 | .TP | |
962a108f | 1433 | .B \-\-detail |
2d465520 NB |
1434 | The device should be an active md device. |
1435 | .B mdadm | |
1436 | will display a detailed description of the array. | |
7e23fc43 | 1437 | .B \-\-brief |
2d465520 | 1438 | or |
7e23fc43 | 1439 | .B \-\-scan |
2d465520 | 1440 | will cause the output to be less detailed and the format to be |
e0d19036 | 1441 | suitable for inclusion in |
9a9dab36 | 1442 | .BR /etc/mdadm.conf . |
feb716e9 NB |
1443 | The exit status of |
1444 | .I mdadm | |
1445 | will normally be 0 unless | |
1446 | .I mdadm | |
93e790af | 1447 | failed to get useful information about the device(s); however, if the |
7e23fc43 | 1448 | .B \-\-test |
feb716e9 NB |
1449 | option is given, then the exit status will be: |
1450 | .RS | |
1451 | .TP | |
1452 | 0 | |
1453 | The array is functioning normally. | |
1454 | .TP | |
1455 | 1 | |
1456 | The array has at least one failed device. | |
1457 | .TP | |
1458 | 2 | |
a77be586 | 1459 | The array has multiple failed devices such that it is unusable. |
feb716e9 NB |
1460 | .TP |
1461 | 4 | |
1462 | There was an error while trying to get information about the device. | |
1463 | .RE | |
cd29a5c8 | 1464 | |
e0d19036 | 1465 | .TP |
962a108f | 1466 | .B \-\-examine |
2d465520 NB |
1467 | The device should be a component of an md array. |
1468 | .B mdadm | |
1469 | will read the md superblock of the device and display the contents. | |
e0d19036 | 1470 | If |
7e23fc43 | 1471 | .B \-\-brief |
93e790af | 1472 | or |
7e23fc43 | 1473 | .B \-\-scan |
93e790af | 1474 | is given, then multiple devices that are components of the one array |
e0d19036 NB |
1475 | are grouped together and reported in a single entry suitable |
1476 | for inclusion in | |
1477 | .BR /etc/mdadm.conf . | |
1478 | ||
2d465520 | 1479 | Having |
7e23fc43 | 1480 | .B \-\-scan |
e0d19036 NB |
1481 | without listing any devices will cause all devices listed in the |
1482 | config file to be examined. | |
1483 | ||
1484 | .TP | |
962a108f | 1485 | .B \-\-stop |
98c6faba NB |
1486 | The devices should be active md arrays which will be deactivated, as |
1487 | long as they are not currently in use. | |
e0d19036 NB |
1488 | |
1489 | .TP | |
962a108f | 1490 | .B \-\-run |
e0d19036 NB |
1491 | This will fully activate a partially assembled md array. |
1492 | ||
1493 | .TP | |
962a108f | 1494 | .B \-\-readonly |
e0d19036 NB |
1495 | This will mark an active array as read-only, providing that it is |
1496 | not currently being used. | |
1497 | ||
1498 | .TP | |
962a108f | 1499 | .B \-\-readwrite |
e0d19036 NB |
1500 | This will change a |
1501 | .B readonly | |
1502 | array back to being read/write. | |
1503 | ||
2d465520 | 1504 | .TP |
962a108f | 1505 | .B \-\-scan |
2d465520 | 1506 | For all operations except |
7e23fc43 PS |
1507 | .BR \-\-examine , |
1508 | .B \-\-scan | |
2d465520 NB |
1509 | will cause the operation to be applied to all arrays listed in |
1510 | .BR /proc/mdstat . | |
1511 | For | |
7e23fc43 PS |
1512 | .BR \-\-examine, |
1513 | .B \-\-scan | |
2d465520 NB |
1514 | causes all devices listed in the config file to be examined. |
1515 | ||
1516 | ||
e0d19036 NB |
1517 | .SH MONITOR MODE |
1518 | ||
cd29a5c8 NB |
1519 | .HP 12 |
1520 | Usage: | |
7e23fc43 | 1521 | .B mdadm \-\-monitor |
e0d19036 NB |
1522 | .I options... devices... |
1523 | ||
cd29a5c8 | 1524 | .PP |
e0d19036 NB |
1525 | This usage causes |
1526 | .B mdadm | |
1527 | to periodically poll a number of md arrays and to report on any events | |
1528 | noticed. | |
1529 | .B mdadm | |
1530 | will never exit once it decides that there are arrays to be checked, | |
1531 | so it should normally be run in the background. | |
1532 | ||
2d465520 NB |
1533 | As well as reporting events, |
1534 | .B mdadm | |
1535 | may move a spare drive from one array to another if they are in the | |
1536 | same | |
1537 | .B spare-group | |
a9d69660 | 1538 | and if the destination array has a failed drive but no spares. |
2d465520 | 1539 | |
e0d19036 NB |
1540 | If any devices are listed on the command line, |
1541 | .B mdadm | |
1542 | will only monitor those devices. Otherwise all arrays listed in the | |
1543 | configuration file will be monitored. Further, if | |
7e23fc43 | 1544 | .B \-\-scan |
e0d19036 NB |
1545 | is given, then any other md devices that appear in |
1546 | .B /proc/mdstat | |
1547 | will also be monitored. | |
1548 | ||
1549 | The result of monitoring the arrays is the generation of events. | |
bd526cee | 1550 | These events are passed to a separate program (if specified) and may |
2d465520 | 1551 | be mailed to a given E-mail address. |
e0d19036 | 1552 | |
93e790af SW |
1553 | When passing events to a program, the program is run once for each event, |
1554 | and is given 2 or 3 command-line arguments: the first is the | |
1555 | name of the event (see below), the second is the name of the | |
bd526cee | 1556 | md device which is affected, and the third is the name of a related |
93e790af | 1557 | device if relevant (such as a component device that has failed). |
cd29a5c8 NB |
1558 | |
1559 | If | |
7e23fc43 | 1560 | .B \-\-scan |
e0d19036 NB |
1561 | is given, then a program or an E-mail address must be specified on the |
1562 | command line or in the config file. If neither are available, then | |
1563 | .B mdadm | |
1564 | will not monitor anything. | |
1565 | Without | |
93e790af | 1566 | .B \-\-scan, |
e0d19036 | 1567 | .B mdadm |
2d465520 | 1568 | will continue monitoring as long as something was found to monitor. If |
e0d19036 NB |
1569 | no program or email is given, then each event is reported to |
1570 | .BR stdout . | |
cd29a5c8 | 1571 | |
e0d19036 NB |
1572 | The different events are: |
1573 | ||
1574 | .RS 4 | |
1575 | .TP | |
1576 | .B DeviceDisappeared | |
2d465520 | 1577 | An md array which previously was configured appears to no longer be |
773135f5 | 1578 | configured. (syslog priority: Critical) |
e0d19036 | 1579 | |
b8f72a62 NB |
1580 | If |
1581 | .I mdadm | |
1582 | was told to monitor an array which is RAID0 or Linear, then it will | |
1583 | report | |
1584 | .B DeviceDisappeared | |
1585 | with the extra information | |
1586 | .BR Wrong-Level . | |
1587 | This is because RAID0 and Linear do not support the device-failed, | |
1588 | hot-spare and resync operations which are monitored. | |
1589 | ||
e0d19036 NB |
1590 | .TP |
1591 | .B RebuildStarted | |
773135f5 | 1592 | An md array started reconstruction. (syslog priority: Warning) |
e0d19036 NB |
1593 | |
1594 | .TP | |
1595 | .BI Rebuild NN | |
1596 | Where | |
1597 | .I NN | |
1598 | is 20, 40, 60, or 80, this indicates that rebuild has passed that many | |
773135f5 | 1599 | percentage of the total. (syslog priority: Warning) |
e0d19036 | 1600 | |
98c6faba NB |
1601 | .TP |
1602 | .B RebuildFinished | |
1603 | An md array that was rebuilding, isn't any more, either because it | |
773135f5 | 1604 | finished normally or was aborted. (syslog priority: Warning) |
98c6faba | 1605 | |
e0d19036 NB |
1606 | .TP |
1607 | .B Fail | |
773135f5 NB |
1608 | An active component device of an array has been marked as |
1609 | faulty. (syslog priority: Critical) | |
e0d19036 NB |
1610 | |
1611 | .TP | |
1612 | .B FailSpare | |
1613 | A spare component device which was being rebuilt to replace a faulty | |
93e790af | 1614 | device has failed. (syslog priority: Critical) |
e0d19036 NB |
1615 | |
1616 | .TP | |
1617 | .B SpareActive | |
1618 | A spare component device which was being rebuilt to replace a faulty | |
98b24a2a | 1619 | device has been successfully rebuilt and has been made active. |
773135f5 | 1620 | (syslog priority: Info) |
e0d19036 NB |
1621 | |
1622 | .TP | |
1623 | .B NewArray | |
1624 | A new md array has been detected in the | |
1625 | .B /proc/mdstat | |
773135f5 | 1626 | file. (syslog priority: Info) |
e0d19036 | 1627 | |
aa88f531 NB |
1628 | .TP |
1629 | .B DegradedArray | |
1630 | A newly noticed array appears to be degraded. This message is not | |
1631 | generated when | |
1632 | .I mdadm | |
1633 | notices a drive failure which causes degradation, but only when | |
1634 | .I mdadm | |
1635 | notices that an array is degraded when it first sees the array. | |
93e790af | 1636 | (syslog priority: Critical) |
aa88f531 | 1637 | |
e0d19036 NB |
1638 | .TP |
1639 | .B MoveSpare | |
1640 | A spare drive has been moved from one array in a | |
1641 | .B spare-group | |
1642 | to another to allow a failed drive to be replaced. | |
773135f5 | 1643 | (syslog priority: Info) |
e0d19036 | 1644 | |
b8f72a62 NB |
1645 | .TP |
1646 | .B SparesMissing | |
1647 | If | |
1648 | .I mdadm | |
1649 | has been told, via the config file, that an array should have a certain | |
1650 | number of spare devices, and | |
1651 | .I mdadm | |
93e790af | 1652 | detects that it has fewer than this number when it first sees the |
b8f72a62 NB |
1653 | array, it will report a |
1654 | .B SparesMissing | |
1655 | message. | |
d1732eeb | 1656 | (syslog priority: Warning) |
b8f72a62 | 1657 | |
98c6faba NB |
1658 | .TP |
1659 | .B TestMessage | |
1660 | An array was found at startup, and the | |
7e23fc43 | 1661 | .B \-\-test |
98c6faba | 1662 | flag was given. |
773135f5 | 1663 | (syslog priority: Info) |
e0d19036 NB |
1664 | .RE |
1665 | ||
1666 | Only | |
93e790af SW |
1667 | .B Fail, |
1668 | .B FailSpare, | |
1669 | .B DegradedArray, | |
1670 | .B SparesMissing | |
e0d19036 | 1671 | and |
98c6faba | 1672 | .B TestMessage |
e0d19036 | 1673 | cause Email to be sent. All events cause the program to be run. |
93e790af | 1674 | The program is run with two or three arguments: the event |
e0d19036 NB |
1675 | name, the array device and possibly a second device. |
1676 | ||
1677 | Each event has an associated array device (e.g. | |
1678 | .BR /dev/md1 ) | |
1679 | and possibly a second device. For | |
1680 | .BR Fail , | |
1681 | .BR FailSpare , | |
1682 | and | |
1683 | .B SpareActive | |
1684 | the second device is the relevant component device. | |
1685 | For | |
1686 | .B MoveSpare | |
1687 | the second device is the array that the spare was moved from. | |
1688 | ||
1689 | For | |
1690 | .B mdadm | |
1691 | to move spares from one array to another, the different arrays need to | |
93e790af | 1692 | be labeled with the same |
e0d19036 NB |
1693 | .B spare-group |
1694 | in the configuration file. The | |
1695 | .B spare-group | |
93e790af | 1696 | name can be any string; it is only necessary that different spare |
2d465520 | 1697 | groups use different names. |
e0d19036 NB |
1698 | |
1699 | When | |
9a9dab36 | 1700 | .B mdadm |
93e790af | 1701 | detects that an array in a spare group has fewer active |
e0d19036 NB |
1702 | devices than necessary for the complete array, and has no spare |
1703 | devices, it will look for another array in the same spare group that | |
1704 | has a full complement of working drive and a spare. It will then | |
1705 | attempt to remove the spare from the second drive and add it to the | |
1706 | first. | |
1707 | If the removal succeeds but the adding fails, then it is added back to | |
1708 | the original array. | |
1709 | ||
dd0781e5 NB |
1710 | .SH GROW MODE |
1711 | The GROW mode is used for changing the size or shape of an active | |
1712 | array. | |
1713 | For this to work, the kernel must support the necessary change. | |
2ae555c3 | 1714 | Various types of growth are being added during 2.6 development, |
dd0781e5 NB |
1715 | including restructuring a raid5 array to have more active devices. |
1716 | ||
dfd4d8ee NB |
1717 | Currently the only support available is to |
1718 | .IP \(bu 4 | |
1719 | change the "size" attribute | |
1720 | for RAID1, RAID5 and RAID6. | |
1721 | .IP \(bu 4 | |
00be0b12 | 1722 | increase the "raid-disks" attribute of RAID1, RAID5, and RAID6. |
dfd4d8ee | 1723 | .IP \(bu 4 |
93e790af | 1724 | add a write-intent bitmap to any array which supports these bitmaps, or |
2ae555c3 | 1725 | remove a write-intent bitmap from such an array. |
dfd4d8ee | 1726 | .PP |
dd0781e5 | 1727 | |
2ae555c3 | 1728 | .SS SIZE CHANGES |
fe80f49b | 1729 | Normally when an array is built the "size" it taken from the smallest |
dd0781e5 NB |
1730 | of the drives. If all the small drives in an arrays are, one at a |
1731 | time, removed and replaced with larger drives, then you could have an | |
1732 | array of large drives with only a small amount used. In this | |
1733 | situation, changing the "size" with "GROW" mode will allow the extra | |
1734 | space to start being used. If the size is increased in this way, a | |
1735 | "resync" process will start to make sure the new parts of the array | |
1736 | are synchronised. | |
1737 | ||
1738 | Note that when an array changes size, any filesystem that may be | |
1739 | stored in the array will not automatically grow to use the space. The | |
1740 | filesystem will need to be explicitly told to use the extra space. | |
1741 | ||
2ae555c3 NB |
1742 | .SS RAID-DEVICES CHANGES |
1743 | ||
dd0781e5 NB |
1744 | A RAID1 array can work with any number of devices from 1 upwards |
1745 | (though 1 is not very useful). There may be times which you want to | |
1746 | increase or decrease the number of active devices. Note that this is | |
1747 | different to hot-add or hot-remove which changes the number of | |
1748 | inactive devices. | |
1749 | ||
1750 | When reducing the number of devices in a RAID1 array, the slots which | |
1751 | are to be removed from the array must already be vacant. That is, the | |
93e790af | 1752 | devices which were in those slots must be failed and removed. |
dd0781e5 NB |
1753 | |
1754 | When the number of devices is increased, any hot spares that are | |
a9d69660 | 1755 | present will be activated immediately. |
dd0781e5 | 1756 | |
2ae555c3 NB |
1757 | Increasing the number of active devices in a RAID5 is much more |
1758 | effort. Every block in the array will need to be read and written | |
1759 | back to a new location. From 2.6.17, the Linux Kernel is able to do | |
1760 | this safely, including restart and interrupted "reshape". | |
1761 | ||
1762 | When relocating the first few stripes on a raid5, it is not possible | |
1763 | to keep the data on disk completely consistent and crash-proof. To | |
1764 | provide the required safety, mdadm disables writes to the array while | |
1765 | this "critical section" is reshaped, and takes a backup of the data | |
1766 | that is in that section. This backup is normally stored in any spare | |
1767 | devices that the array has, however it can also be stored in a | |
1768 | separate file specified with the | |
7e23fc43 | 1769 | .B \-\-backup\-file |
2ae555c3 NB |
1770 | option. If this option is used, and the system does crash during the |
1771 | critical period, the same file must be passed to | |
7e23fc43 | 1772 | .B \-\-assemble |
2ae555c3 NB |
1773 | to restore the backup and reassemble the array. |
1774 | ||
1775 | .SS BITMAP CHANGES | |
1776 | ||
1777 | A write-intent bitmap can be added to, or removed from, an active | |
93e790af | 1778 | array. Either internal bitmaps, or bitmaps stored in a separate file, |
fe80f49b NB |
1779 | can be added. Note that if you add a bitmap stored in a file which is |
1780 | in a filesystem that is on the raid array being affected, the system | |
1781 | will deadlock. The bitmap must be on a separate filesystem. | |
1782 | ||
8382f19b NB |
1783 | .SH INCREMENTAL MODE |
1784 | ||
1785 | .HP 12 | |
1786 | Usage: | |
7e23fc43 PS |
1787 | .B mdadm \-\-incremental |
1788 | .RB [ \-\-run ] | |
1789 | .RB [ \-\-quiet ] | |
8382f19b NB |
1790 | .I component-device |
1791 | .HP 12 | |
1792 | Usage: | |
7e23fc43 | 1793 | .B mdadm \-\-incremental \-\-rebuild |
8382f19b NB |
1794 | .HP 12 |
1795 | Usage: | |
7e23fc43 | 1796 | .B mdadm \-\-incremental \-\-run \-\-scan |
8382f19b NB |
1797 | |
1798 | ||
1799 | .PP | |
1800 | This mode is designed to be used in conjunction with a device | |
1801 | discovery system. As devices are found in a system, they can be | |
1802 | passed to | |
7e23fc43 | 1803 | .B "mdadm \-\-incremental" |
8382f19b NB |
1804 | to be conditionally added to an appropriate array. |
1805 | ||
1806 | .I mdadm | |
1807 | performs a number of tests to determine if the device is part of an | |
93e790af | 1808 | array, and which array it should be part of. If an appropriate array |
8382f19b NB |
1809 | is found, or can be created, |
1810 | .I mdadm | |
1811 | adds the device to the array and conditionally starts the array. | |
1812 | ||
1813 | Note that | |
1814 | .I mdadm | |
1815 | will only add devices to an array which were previously working | |
1816 | (active or spare) parts of that array. It does not currently support | |
1817 | automatic inclusion of a new drive as a spare in some array. | |
1818 | ||
7e23fc43 | 1819 | .B "mdadm \-\-incremental" |
93e790af SW |
1820 | requires a bug-fix in all kernels through 2.6.19. |
1821 | Hopefully, this will be fixed in 2.6.20; alternately, apply the patch | |
8382f19b NB |
1822 | which is included with the mdadm source distribution. If |
1823 | .I mdadm | |
1824 | detects that this bug is present, it will abort any attempt to use | |
7e23fc43 | 1825 | .BR \-\-incremental . |
8382f19b NB |
1826 | |
1827 | The tests that | |
1828 | .I mdadm | |
1829 | makes are as follow: | |
1830 | .IP + | |
1831 | Is the device permitted by | |
1832 | .BR mdadm.conf ? | |
1833 | That is, is it listed in a | |
1834 | .B DEVICES | |
1835 | line in that file. If | |
1836 | .B DEVICES | |
1837 | is absent then the default it to allow any device. Similar if | |
1838 | .B DEVICES | |
1839 | contains the special word | |
1840 | .B partitions | |
1841 | then any device is allowed. Otherwise the device name given to | |
1842 | .I mdadm | |
1843 | must match one of the names or patterns in a | |
1844 | .B DEVICES | |
1845 | line. | |
1846 | ||
1847 | .IP + | |
1848 | Does the device have a valid md superblock. If a specific metadata | |
1849 | version is request with | |
7e23fc43 | 1850 | .B \-\-metadata |
8382f19b | 1851 | or |
7e23fc43 | 1852 | .B \-e |
8382f19b NB |
1853 | then only that style of metadata is accepted, otherwise |
1854 | .I mdadm | |
1855 | finds any known version of metadata. If no | |
1856 | .I md | |
1857 | metadata is found, the device is rejected. | |
1858 | ||
1859 | .IP + | |
1860 | Does the metadata match an expected array? | |
1861 | The metadata can match in two ways. Either there is an array listed | |
1862 | in | |
1863 | .B mdadm.conf | |
1864 | which identifies the array (either by UUID, by name, by device list, | |
93e790af | 1865 | or by minor-number), or the array was created with a |
8382f19b | 1866 | .B homehost |
93e790af | 1867 | specified and that |
8382f19b | 1868 | .B homehost |
93e790af | 1869 | matches the one in |
8382f19b NB |
1870 | .B mdadm.conf |
1871 | or on the command line. | |
1872 | If | |
1873 | .I mdadm | |
1874 | is not able to positively identify the array as belonging to the | |
1875 | current host, the device will be rejected. | |
1876 | ||
1877 | .IP + | |
1878 | .I mdadm | |
93e790af | 1879 | keeps a list of arrays that it has partially assembled in |
8382f19b NB |
1880 | .B /var/run/mdadm/map |
1881 | (or | |
1882 | .B /var/run/mdadm.map | |
1883 | if the directory doesn't exist). If no array exists which matches | |
1884 | the metadata on the new device, | |
1885 | .I mdadm | |
1886 | must choose a device name and unit number. It does this based on any | |
1887 | name given in | |
1888 | .B mdadm.conf | |
1889 | or any name information stored in the metadata. If this name | |
1890 | suggests a unit number, that number will be used, otherwise a free | |
1891 | unit number will be chosen. Normally | |
1892 | .I mdadm | |
1893 | will prefer to create a partitionable array, however if the | |
1894 | .B CREATE | |
1895 | line in | |
1896 | .B mdadm.conf | |
1897 | suggests that a non-partitionable array is preferred, that will be | |
1898 | honoured. | |
1899 | ||
1900 | .IP + | |
1901 | Once an appropriate array is found or created and the device is added, | |
1902 | .I mdadm | |
1903 | must decide if the array is ready to be started. It will | |
1904 | normally compare the number of available (non-spare) devices to the | |
1905 | number of devices that the metadata suggests need to be active. If | |
1906 | there are at least that many, the array will be started. This means | |
1907 | that if any devices are missing the array will not be restarted. | |
1908 | ||
1909 | As an alternative, | |
7e23fc43 | 1910 | .B \-\-run |
8382f19b NB |
1911 | may be passed to |
1912 | .B mdadm | |
1913 | in which case the array will be run as soon as there are enough | |
1914 | devices present for the data to be accessible. For a raid1, that | |
1915 | means one device will start the array. For a clean raid5, the array | |
1916 | will be started as soon as all but one drive is present. | |
1917 | ||
93e790af | 1918 | Note that neither of these approaches is really ideal. If it can |
8382f19b NB |
1919 | be known that all device discovery has completed, then |
1920 | .br | |
7e23fc43 | 1921 | .B " mdadm \-IRs" |
8382f19b NB |
1922 | .br |
1923 | can be run which will try to start all arrays that are being | |
1924 | incrementally assembled. They are started in "read-auto" mode in | |
1925 | which they are read-only until the first write request. This means | |
1926 | that no metadata updates are made and no attempt at resync or recovery | |
1927 | happens. Further devices that are found before the first write can | |
1928 | still be added safely. | |
1929 | ||
2d465520 NB |
1930 | .SH EXAMPLES |
1931 | ||
7e23fc43 | 1932 | .B " mdadm \-\-query /dev/name-of-device" |
2d465520 | 1933 | .br |
5787fa49 NB |
1934 | This will find out if a given device is a raid array, or is part of |
1935 | one, and will provide brief information about the device. | |
2d465520 | 1936 | |
7e23fc43 | 1937 | .B " mdadm \-\-assemble \-\-scan" |
2d465520 | 1938 | .br |
93e790af | 1939 | This will assemble and start all arrays listed in the standard config |
5787fa49 | 1940 | file. This command will typically go in a system startup file. |
2d465520 | 1941 | |
7e23fc43 | 1942 | .B " mdadm \-\-stop \-\-scan" |
5787fa49 | 1943 | .br |
93e790af | 1944 | This will shut down all arrays that can be shut down (i.e. are not |
19f8b8fc | 1945 | currently in use). This will typically go in a system shutdown script. |
2d465520 | 1946 | |
7e23fc43 | 1947 | .B " mdadm \-\-follow \-\-scan \-\-delay=120" |
2d465520 | 1948 | .br |
5787fa49 NB |
1949 | If (and only if) there is an Email address or program given in the |
1950 | standard config file, then | |
1951 | monitor the status of all arrays listed in that file by | |
1952 | polling them ever 2 minutes. | |
2d465520 | 1953 | |
7e23fc43 | 1954 | .B " mdadm \-\-create /dev/md0 \-\-level=1 \-\-raid\-devices=2 /dev/hd[ac]1" |
2d465520 | 1955 | .br |
5787fa49 | 1956 | Create /dev/md0 as a RAID1 array consisting of /dev/hda1 and /dev/hdc1. |
2d465520 | 1957 | |
2d465520 | 1958 | .br |
7e23fc43 | 1959 | .B " echo 'DEVICE /dev/hd*[0\-9] /dev/sd*[0\-9]' > mdadm.conf" |
2d465520 | 1960 | .br |
7e23fc43 | 1961 | .B " mdadm \-\-detail \-\-scan >> mdadm.conf" |
2d465520 | 1962 | .br |
5787fa49 NB |
1963 | This will create a prototype config file that describes currently |
1964 | active arrays that are known to be made from partitions of IDE or SCSI drives. | |
2d465520 NB |
1965 | This file should be reviewed before being used as it may |
1966 | contain unwanted detail. | |
1967 | ||
7e23fc43 | 1968 | .B " echo 'DEVICE /dev/hd[a\-z] /dev/sd*[a\-z]' > mdadm.conf" |
2d465520 | 1969 | .br |
7e23fc43 | 1970 | .B " mdadm \-\-examine \-\-scan \-\-config=mdadm.conf >> mdadm.conf" |
93e790af SW |
1971 | .br |
1972 | This will find arrays which could be assembled from existing IDE and | |
1973 | SCSI whole drives (not partitions), and store the information in the | |
5787fa49 | 1974 | format of a config file. |
2d465520 NB |
1975 | This file is very likely to contain unwanted detail, particularly |
1976 | the | |
1977 | .B devices= | |
5787fa49 NB |
1978 | entries. It should be reviewed and edited before being used as an |
1979 | actual config file. | |
2d465520 | 1980 | |
7e23fc43 | 1981 | .B " mdadm \-\-examine \-\-brief \-\-scan \-\-config=partitions" |
2d465520 | 1982 | .br |
7e23fc43 | 1983 | .B " mdadm \-Ebsc partitions" |
5787fa49 NB |
1984 | .br |
1985 | Create a list of devices by reading | |
1986 | .BR /proc/partitions , | |
1987 | scan these for RAID superblocks, and printout a brief listing of all | |
93e790af | 1988 | that were found. |
2d465520 | 1989 | |
7e23fc43 | 1990 | .B " mdadm \-Ac partitions \-m 0 /dev/md0" |
2d465520 | 1991 | .br |
5787fa49 NB |
1992 | Scan all partitions and devices listed in |
1993 | .BR /proc/partitions | |
1994 | and assemble | |
1995 | .B /dev/md0 | |
1996 | out of all such devices with a RAID superblock with a minor number of 0. | |
2d465520 | 1997 | |
7e23fc43 | 1998 | .B " mdadm \-\-monitor \-\-scan \-\-daemonise > /var/run/mdadm" |
d013a55e NB |
1999 | .br |
2000 | If config file contains a mail address or alert program, run mdadm in | |
2001 | the background in monitor mode monitoring all md devices. Also write | |
2002 | pid of mdadm daemon to | |
2003 | .BR /var/run/mdadm . | |
2004 | ||
7e23fc43 | 2005 | .B " mdadm \-Iq /dev/somedevice" |
8382f19b NB |
2006 | .br |
2007 | Try to incorporate newly discovered device into some array as | |
2008 | appropriate. | |
2009 | ||
7e23fc43 | 2010 | .B " mdadm \-\-incremental \-\-rebuild \-\-run \-\-scan" |
8382f19b NB |
2011 | .br |
2012 | Rebuild the array map from any current arrays, and then start any that | |
2013 | can be started. | |
2014 | ||
b80da661 NB |
2015 | .B " mdadm /dev/md4 --fail detached --remove detached" |
2016 | .br | |
2017 | Any devices which are components of /dev/md4 will be marked as faulty | |
2018 | and then remove from the array. | |
2019 | ||
7e23fc43 | 2020 | .B " mdadm \-\-create \-\-help" |
2d465520 | 2021 | .br |
2ae555c3 | 2022 | Provide help about the Create mode. |
2d465520 | 2023 | |
7e23fc43 | 2024 | .B " mdadm \-\-config \-\-help" |
5787fa49 NB |
2025 | .br |
2026 | Provide help about the format of the config file. | |
2d465520 | 2027 | |
7e23fc43 | 2028 | .B " mdadm \-\-help" |
5787fa49 NB |
2029 | .br |
2030 | Provide general help. | |
cd29a5c8 | 2031 | |
cd29a5c8 NB |
2032 | |
2033 | .SH FILES | |
2034 | ||
2035 | .SS /proc/mdstat | |
2036 | ||
2ae555c3 NB |
2037 | If you're using the |
2038 | .B /proc | |
cd29a5c8 NB |
2039 | filesystem, |
2040 | .B /proc/mdstat | |
2d465520 NB |
2041 | lists all active md devices with information about them. |
2042 | .B mdadm | |
2043 | uses this to find arrays when | |
7e23fc43 | 2044 | .B \-\-scan |
2d465520 NB |
2045 | is given in Misc mode, and to monitor array reconstruction |
2046 | on Monitor mode. | |
2047 | ||
cd29a5c8 | 2048 | |
9a9dab36 | 2049 | .SS /etc/mdadm.conf |
cd29a5c8 | 2050 | |
11a3e71d NB |
2051 | The config file lists which devices may be scanned to see if |
2052 | they contain MD super block, and gives identifying information | |
2053 | (e.g. UUID) about known MD arrays. See | |
2054 | .BR mdadm.conf (5) | |
2055 | for more details. | |
cd29a5c8 | 2056 | |
8382f19b NB |
2057 | .SS /var/run/mdadm/map |
2058 | When | |
7e23fc43 | 2059 | .B \-\-incremental |
93e790af | 2060 | mode is used, this file gets a list of arrays currently being created. |
8382f19b NB |
2061 | If |
2062 | .B /var/run/mdadm | |
2063 | does not exist as a directory, then | |
2064 | .B /var/run/mdadm.map | |
2065 | is used instead. | |
2066 | ||
48f7b27a NB |
2067 | .SH DEVICE NAMES |
2068 | ||
2069 | While entries in the /dev directory can have any format you like, | |
2070 | .I mdadm | |
2071 | has an understanding of 'standard' formats which it uses to guide its | |
2072 | behaviour when creating device files via the | |
7e23fc43 | 2073 | .B \-\-auto |
48f7b27a NB |
2074 | option. |
2075 | ||
2076 | The standard names for non-partitioned arrays (the only sort of md | |
93e790af | 2077 | array available in 2.4 and earlier) are either of |
48f7b27a NB |
2078 | .IP |
2079 | /dev/mdNN | |
2080 | .br | |
2081 | /dev/md/NN | |
2082 | .PP | |
2083 | where NN is a number. | |
2084 | The standard names for partitionable arrays (as available from 2.6 | |
93e790af | 2085 | onwards) are either of |
48f7b27a NB |
2086 | .IP |
2087 | /dev/md/dNN | |
2088 | .br | |
2089 | /dev/md_dNN | |
2090 | .PP | |
2091 | Partition numbers should be indicated by added "pMM" to these, thus "/dev/md/d1p2". | |
52826846 | 2092 | |
2d465520 NB |
2093 | .SH NOTE |
2094 | .B mdadm | |
2095 | was previously known as | |
2096 | .BR mdctl . | |
a9d69660 NB |
2097 | .P |
2098 | .B mdadm | |
2099 | is completely separate from the | |
2100 | .B raidtools | |
2101 | package, and does not use the | |
2102 | .I /etc/raidtab | |
2103 | configuration file at all. | |
2104 | ||
52826846 | 2105 | .SH SEE ALSO |
cd29a5c8 NB |
2106 | For information on the various levels of |
2107 | RAID, check out: | |
2108 | ||
2109 | .IP | |
7e23fc43 PS |
2110 | .UR http://ostenfeld.dk/~jakob/Software\-RAID.HOWTO/ |
2111 | http://ostenfeld.dk/~jakob/Software\-RAID.HOWTO/ | |
cd29a5c8 | 2112 | .UE |
a9d69660 NB |
2113 | '''.PP |
2114 | '''for new releases of the RAID driver check out: | |
2115 | ''' | |
2116 | '''.IP | |
2117 | '''.UR ftp://ftp.kernel.org/pub/linux/kernel/people/mingo/raid-patches | |
2118 | '''ftp://ftp.kernel.org/pub/linux/kernel/people/mingo/raid-patches | |
2119 | '''.UE | |
2120 | '''.PP | |
2121 | '''or | |
2122 | '''.IP | |
2123 | '''.UR http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/ | |
2124 | '''http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/ | |
2125 | '''.UE | |
cd29a5c8 | 2126 | .PP |
2ae555c3 | 2127 | The latest version of |
a9d69660 NB |
2128 | .I mdadm |
2129 | should always be available from | |
cd29a5c8 | 2130 | .IP |
a9d69660 NB |
2131 | .UR http://www.kernel.org/pub/linux/utils/raid/mdadm/ |
2132 | http://www.kernel.org/pub/linux/utils/raid/mdadm/ | |
cd29a5c8 NB |
2133 | .UE |
2134 | .PP | |
a9d69660 NB |
2135 | .IR mdadm.conf (5), |
2136 | .IR md (4). | |
56eb10c0 | 2137 | .PP |
52826846 NB |
2138 | .IR raidtab (5), |
2139 | .IR raid0run (8), | |
2140 | .IR raidstop (8), | |
a9d69660 | 2141 | .IR mkraid (8). |