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