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