]>
Commit | Line | Data |
---|---|---|
52826846 | 1 | .\" -*- nroff -*- |
b5e64645 | 2 | .TH MDADM 8 "" v1.8.0 |
52826846 | 3 | .SH NAME |
9a9dab36 | 4 | mdadm \- manage MD devices |
cd29a5c8 NB |
5 | .I aka |
6 | Linux Software Raid. | |
7 | ||
52826846 NB |
8 | .SH SYNOPSIS |
9 | ||
e0d19036 | 10 | .BI mdadm " [mode] <raiddevice> [options] <component-devices>" |
52826846 NB |
11 | |
12 | .SH DESCRIPTION | |
13 | RAID devices are virtual devices created from two or more | |
cd29a5c8 NB |
14 | real block devices. This allows multiple devices (typically disk |
15 | drives or partitions there-of) to be combined into a single device to | |
16 | hold (for example) a single filesystem. | |
2d465520 | 17 | Some RAID levels include redundancy and so can survive some degree of |
cd29a5c8 NB |
18 | device failure. |
19 | ||
2d465520 NB |
20 | Linux Software RAID devices are implemented through the md (Multiple |
21 | Devices) device driver. | |
cd29a5c8 NB |
22 | |
23 | Currently, Linux supports | |
24 | .B LINEAR | |
25 | md devices, | |
26 | .B RAID0 | |
27 | (striping), | |
28 | .B RAID1 | |
29 | (mirroring), | |
d013a55e NB |
30 | .BR RAID4 , |
31 | .BR RAID5 , | |
98c6faba | 32 | .BR RAID6 , |
b5e64645 | 33 | .BR MULTIPATH , |
cd29a5c8 | 34 | and |
b5e64645 | 35 | .BR FAULTY . |
d013a55e NB |
36 | |
37 | .B MULTIPATH is not a Software RAID mechanism, but does involve | |
38 | multiple devices. For | |
39 | .B MULTIPATH | |
40 | each device is a path to one common physical storage device. | |
41 | ||
b5e64645 NB |
42 | .B FAULTY is also no true RAID, and it only involves one device. It |
43 | provides a layer over a true device that can be used to inject faults. | |
52826846 | 44 | |
9a9dab36 | 45 | .B mdadm |
11a3e71d NB |
46 | is a program that can be used to create, manage, and monitor |
47 | MD devices. As | |
cd29a5c8 NB |
48 | such it provides a similar set of functionality to the |
49 | .B raidtools | |
50 | packages. | |
51 | The key differences between | |
9a9dab36 | 52 | .B mdadm |
cd29a5c8 NB |
53 | and |
54 | .B raidtools | |
55 | are: | |
56 | .IP \(bu 4 | |
9a9dab36 | 57 | .B mdadm |
cd29a5c8 NB |
58 | is a single program and not a collection of programs. |
59 | .IP \(bu 4 | |
9a9dab36 | 60 | .B mdadm |
cd29a5c8 | 61 | can perform (almost) all of its functions without having a |
5787fa49 | 62 | configuration file and does not use one by default. Also |
2d465520 NB |
63 | .B mdadm |
64 | helps with management of the configuration | |
cd29a5c8 NB |
65 | file. |
66 | .IP \(bu 4 | |
9a9dab36 | 67 | .B mdadm |
e0d19036 | 68 | can provide information about your arrays (through Query, Detail, and Examine) |
cd29a5c8 NB |
69 | that |
70 | .B raidtools | |
71 | cannot. | |
5787fa49 NB |
72 | .P |
73 | .I mdadm | |
74 | does not use | |
75 | .IR /etc/raidtab , | |
76 | the | |
77 | .B raidtools | |
78 | configuration file, at all. It has a different configuration file | |
79 | with a different format and an different purpose. | |
52826846 NB |
80 | |
81 | .SH MODES | |
dd0781e5 | 82 | mdadm has 7 major modes of operation: |
cd29a5c8 NB |
83 | .TP |
84 | .B Assemble | |
85 | Assemble the parts of a previously created | |
52826846 NB |
86 | array into an active array. Components can be explicitly given |
87 | or can be searched for. | |
9a9dab36 | 88 | .B mdadm |
cd29a5c8 NB |
89 | checks that the components |
90 | do form a bona fide array, and can, on request, fiddle superblock | |
91 | information so as to assemble a faulty array. | |
92 | ||
93 | .TP | |
94 | .B Build | |
95 | Build a legacy array without per-device superblocks. | |
96 | ||
97 | .TP | |
98 | .B Create | |
99 | Create a new array with per-device superblocks. | |
100 | '''It can progress | |
101 | '''in several step create-add-add-run or it can all happen with one command. | |
102 | ||
103 | .TP | |
e0d19036 NB |
104 | .B Manage |
105 | This is for doing things to specific components of an array such as | |
106 | adding new spares and removing faulty devices. | |
cd29a5c8 NB |
107 | |
108 | .TP | |
e0d19036 NB |
109 | .B Misc |
110 | This mode allows operations on independent devices such as examine MD | |
111 | superblocks, erasing old superblocks and stopping active arrays. | |
cd29a5c8 NB |
112 | |
113 | .TP | |
114 | .B "Follow or Monitor" | |
5787fa49 | 115 | Monitor one or more md devices and act on any state changes. This is |
98c6faba NB |
116 | only meaningful for raid1, 4, 5, 6 or multipath arrays as |
117 | only these have interesting state. raid0 or linear never have | |
118 | missing, spare, or failed drives, so there is nothing to monitor. | |
5787fa49 | 119 | |
dd0781e5 NB |
120 | .TP |
121 | .B "Grow" | |
122 | Grow (or shrink) an array, or otherwise reshape it in some way. | |
123 | Currently supported growth options including changing the active size | |
124 | of componenet devices in RAID level 1/4/5/6 and changing the number of | |
125 | active devices in RAID1. | |
cd29a5c8 | 126 | |
52826846 NB |
127 | .SH OPTIONS |
128 | ||
129 | Available options are: | |
130 | ||
cd29a5c8 NB |
131 | .TP |
132 | .BR -A ", " --assemble | |
2d465520 | 133 | Assemble a pre-existing array. |
52826846 | 134 | |
cd29a5c8 NB |
135 | .TP |
136 | .BR -B ", " --build | |
137 | Build a legacy array without superblocks. | |
52826846 | 138 | |
cd29a5c8 NB |
139 | .TP |
140 | .BR -C ", " --create | |
141 | Create a new array. | |
52826846 | 142 | |
e0d19036 NB |
143 | .TP |
144 | .BR -Q ", " --query | |
145 | Examine a device to see | |
146 | (1) if it is an md device and (2) if it is a component of an md | |
147 | array. | |
148 | Information about what is discovered is presented. | |
149 | ||
cd29a5c8 NB |
150 | .TP |
151 | .BR -D ", " --detail | |
152 | Print detail of one or more md devices. | |
52826846 | 153 | |
cd29a5c8 NB |
154 | .TP |
155 | .BR -E ", " --examine | |
156 | Print content of md superblock on device(s). | |
52826846 | 157 | |
cd29a5c8 NB |
158 | .TP |
159 | .BR -F ", " --follow ", " --monitor | |
160 | Select | |
161 | .B Monitor | |
162 | mode. | |
52826846 | 163 | |
dd0781e5 NB |
164 | .TP |
165 | .BR -G ", " --grow | |
166 | Change the size or shape of an active array. | |
167 | ||
cd29a5c8 NB |
168 | .TP |
169 | .BR -h ", " --help | |
56eedc1a NB |
170 | Display help message or, after above option, mode specific help |
171 | message. | |
172 | ||
173 | .TP | |
174 | .B --help-options | |
175 | Display more detailed help about command line parsing and some commonly | |
176 | used options. | |
52826846 | 177 | |
cd29a5c8 NB |
178 | .TP |
179 | .BR -V ", " --version | |
9a9dab36 | 180 | Print version information for mdadm. |
52826846 | 181 | |
cd29a5c8 NB |
182 | .TP |
183 | .BR -v ", " --verbose | |
184 | Be more verbose about what is happening. | |
52826846 | 185 | |
cd29a5c8 NB |
186 | .TP |
187 | .BR -b ", " --brief | |
188 | Be less verbose. This is used with | |
189 | .B --detail | |
190 | and | |
191 | .BR --examine . | |
52826846 | 192 | |
e0d19036 NB |
193 | .TP |
194 | .BR -f ", " --force | |
195 | Be more forceful about certain operations. See the various modes of | |
196 | the exact meaning of this option in different contexts. | |
197 | ||
198 | .TP | |
199 | .BR -c ", " --config= | |
200 | Specify the config file. Default is | |
201 | .BR /etc/mdadm.conf . | |
5787fa49 NB |
202 | If the config file given is |
203 | .B partitions | |
204 | then nothing will be read, but | |
205 | .I mdadm | |
206 | will act as though the config file contained exactly | |
207 | .B "DEVICE partitions" | |
208 | and will read | |
209 | .B /proc/partitions | |
210 | to find a list of devices to scan. | |
d013a55e NB |
211 | If the word |
212 | .B none | |
213 | is given for the config file, then | |
214 | .I mdadm | |
215 | will act as though the config file were empty. | |
e0d19036 NB |
216 | |
217 | .TP | |
218 | .BR -s ", " --scan | |
219 | scan config file or | |
220 | .B /proc/mdstat | |
221 | for missing information. | |
222 | In general, this option gives | |
223 | .B mdadm | |
224 | permission to get any missing information, like component devices, | |
225 | array devices, array identities, and alert destination from the | |
226 | configuration file: | |
227 | .BR /etc/mdadm.conf . | |
228 | One exception is MISC mode when using | |
229 | .B --detail | |
230 | or | |
231 | .B --stop | |
232 | in which case | |
233 | .B --scan | |
234 | says to get a list of array devices from | |
235 | .BR /proc/mdstat . | |
236 | ||
cd29a5c8 | 237 | .SH For create or build: |
52826846 | 238 | |
cd29a5c8 NB |
239 | .TP |
240 | .BR -c ", " --chunk= | |
241 | Specify chunk size of kibibytes. The default is 64. | |
52826846 | 242 | |
cd29a5c8 NB |
243 | .TP |
244 | .BR --rounding= | |
245 | Specify rounding factor for linear array (==chunk size) | |
52826846 | 246 | |
cd29a5c8 NB |
247 | .TP |
248 | .BR -l ", " --level= | |
aa88f531 NB |
249 | Set raid level. When used with |
250 | .IR --create , | |
98c6faba | 251 | options are: linear, raid0, 0, stripe, raid1, 1, mirror, raid4, 4, |
b5e64645 | 252 | raid5, 5, raid6, 6, multipath, mp, fautly. Obviously some of these are synonymous. |
aa88f531 NB |
253 | |
254 | When used with | |
255 | .IR --build , | |
256 | only linear, raid0, 0, stripe are valid. | |
52826846 | 257 | |
cd29a5c8 NB |
258 | .TP |
259 | .BR -p ", " --parity= | |
260 | Set raid5 parity algorithm. Options are: | |
2d465520 NB |
261 | left-asymmetric, |
262 | left-symmetric, | |
263 | right-asymmetric, | |
264 | right-symmetric, | |
265 | la, ra, ls, rs. The default is left-symmetric. | |
52826846 | 266 | |
b5e64645 NB |
267 | This option is also used to set the failure mode for |
268 | .IR faulty . | |
269 | The options are: | |
270 | write-transient, | |
271 | wt, | |
272 | read-transient, | |
273 | rt, | |
274 | write-presistent, | |
275 | wp, | |
276 | read-persistent, | |
277 | rp, | |
278 | write-all, | |
279 | read-fixable, | |
280 | rf, | |
281 | clear, | |
282 | flush, | |
283 | none. | |
284 | ||
285 | Each mode can be followed by a number which is used as a period | |
286 | between fault generation. Without a number, the fault is generated | |
287 | once on the first relevant request. With a number, the fault will be | |
288 | generated after that many request, and will continue to be generated | |
289 | every time the period elapses. | |
290 | ||
291 | Multiple failure modes can be current simultaneously by using the | |
292 | "--grow" option to set subsequent failure modes. | |
293 | ||
294 | "clear" or "none" will remove any pending or periodic failure modes, | |
295 | and "flush" will clear any persistant faults. | |
296 | ||
297 | To set the parity with "--grow", the level of the array ("faulty") | |
298 | must be specified before the fault mode is specified. | |
299 | ||
cd29a5c8 NB |
300 | .TP |
301 | .BR --layout= | |
302 | same as --parity | |
52826846 | 303 | |
cd29a5c8 | 304 | .TP |
b83d95f3 | 305 | .BR -n ", " --raid-devices= |
5787fa49 NB |
306 | Specify the number of active devices in the array. This, plus the |
307 | number of spare devices (see below) must equal the number of | |
308 | .I component-devices | |
d013a55e | 309 | (including "\fBmissing\fP" devices) |
dd0781e5 NB |
310 | that are listed on the command line for |
311 | .BR --create . | |
312 | Setting a value of 1 is probably | |
aa88f531 NB |
313 | a mistake and so requires that |
314 | .B --force | |
315 | be specified first. A value of 1 will then be allowed for linear, | |
316 | multipath, raid0 and raid1. It is never allowed for raid4 or raid5. | |
317 | .br | |
dd0781e5 NB |
318 | This number can only be changed using |
319 | .B --grow | |
320 | for RAID1 arrays, and only on kernels which provide necessary support. | |
cd29a5c8 NB |
321 | |
322 | .TP | |
b83d95f3 | 323 | .BR -x ", " --spare-devices= |
5787fa49 NB |
324 | Specify the number of spare (eXtra) devices in the initial array. |
325 | Spares can also be added | |
326 | and removed later. The number of component devices listed | |
327 | on the command line must equal the number of raid devices plus the | |
328 | number of spare devices. | |
329 | ||
cd29a5c8 NB |
330 | |
331 | .TP | |
332 | .BR -z ", " --size= | |
98c6faba | 333 | Amount (in Kibibytes) of space to use from each drive in RAID1/4/5/6. |
cd29a5c8 NB |
334 | This must be a multiple of the chunk size, and must leave about 128Kb |
335 | of space at the end of the drive for the RAID superblock. | |
336 | If this is not specified | |
337 | (as it normally is not) the smallest drive (or partition) sets the | |
338 | size, though if there is a variance among the drives of greater than 1%, a warning is | |
339 | issued. | |
52826846 | 340 | |
dd0781e5 NB |
341 | This value can be set with |
342 | .B --grow | |
343 | for RAID level 1/4/5/6. If the array was created with a size smaller | |
344 | than the currently active drives, the extra space can be accessed | |
345 | using | |
346 | .BR --grow . | |
347 | ||
348 | .TP | |
349 | .BR --assume-clean | |
350 | Tell | |
351 | .I mdadm | |
352 | that the array pre-existed and is known to be clean. This is only | |
353 | really useful for Building RAID1 array. Only use this if you really | |
354 | know what you are doing. This is currently only supported for --build. | |
355 | ||
356 | .TP | |
357 | .BR -R ", " --run | |
358 | Insist that | |
359 | .I mdadm | |
360 | run the array, even if some of the components | |
361 | appear to be active in another array or filesystem. Normally | |
362 | .I mdadm | |
363 | will ask for confirmation before including such components in an | |
364 | array. This option causes that question to be suppressed. | |
365 | ||
366 | .TP | |
367 | .BR -f ", " --force | |
368 | Insist that | |
369 | .I mdadm | |
370 | accept the geometry and layout specified without question. Normally | |
371 | .I mdadm | |
372 | will not allow creation of an array with only one device, and will try | |
373 | to create a raid5 array with one missing drive (as this makes the | |
374 | initial resync work faster). With | |
375 | .BR --force , | |
376 | .I mdadm | |
377 | will not try to be so clever. | |
378 | ||
379 | .TP | |
380 | .BR -a ", " "--auto{=no,yes,md,mdp,part,p}{NN}" | |
381 | Instruct mdadm to create the device file if needed, and to allocate | |
382 | an unused minor number. "yes" or "md" causes a non-partitionable array | |
383 | to be used. "mdp", "part" or "p" causes a partitionable array (2.6 and | |
384 | later) to be used. The argumentment can also come immediately after | |
385 | "-a". e.g. "-ap". | |
386 | ||
387 | For partitionable arrays, | |
388 | .I mdadm | |
389 | will create the device file for the whole array and for the first 4 | |
390 | partitions. A different number of partitions can be specified at the | |
391 | end of this option (e.g. | |
392 | .BR --auto=p7 ). | |
393 | If the device name ends with a digit, the partition names add an | |
394 | underscore, a 'p', and a number, e.g. "/dev/home1_p3". If there is no | |
395 | trailing digit, then the partition names just have a number added, | |
396 | e.g. "/dev/scratch3". | |
397 | ||
52826846 NB |
398 | .SH For assemble: |
399 | ||
cd29a5c8 NB |
400 | .TP |
401 | .BR -u ", " --uuid= | |
402 | uuid of array to assemble. Devices which don't have this uuid are | |
403 | excluded | |
404 | ||
405 | .TP | |
406 | .BR -m ", " --super-minor= | |
407 | Minor number of device that array was created for. Devices which | |
408 | don't have this minor number are excluded. If you create an array as | |
2d465520 | 409 | /dev/md1, then all superblocks will contain the minor number 1, even if |
cd29a5c8 NB |
410 | the array is later assembled as /dev/md2. |
411 | ||
d013a55e NB |
412 | Giving the literal word "dev" for |
413 | .B --super-minor | |
414 | will cause | |
415 | .I mdadm | |
416 | to use the minor number of the md device that is being assembled. | |
417 | e.g. when assembling | |
418 | .BR /dev/md0 , | |
419 | .M --super-minor=dev | |
420 | will look for super blocks with a minor number of 0. | |
421 | ||
cd29a5c8 NB |
422 | .TP |
423 | .BR -f ", " --force | |
52826846 NB |
424 | Assemble the array even if some superblocks appear out-of-date |
425 | ||
cd29a5c8 NB |
426 | .TP |
427 | .BR -R ", " --run | |
428 | Attempt to start the array even if fewer drives were given than are | |
429 | needed for a full array. Normally if not all drives are found and | |
430 | .B --scan | |
431 | is not used, then the array will be assembled but not started. | |
432 | With | |
433 | .B --run | |
434 | an attempt will be made to start it anyway. | |
52826846 | 435 | |
dd0781e5 NB |
436 | .TP |
437 | .BR -a ", " "--auto{=no,yes,md,mdp,part}" | |
438 | See this option under Create and Build options. | |
439 | ||
5787fa49 NB |
440 | .TP |
441 | .BR -U ", " --update= | |
442 | Update the superblock on each device while assembling the array. The | |
feb716e9 NB |
443 | argument given to this flag can be one of |
444 | .BR sparc2.2 , | |
445 | .BR summaries , | |
e5329c37 | 446 | .BR resync , |
5787fa49 NB |
447 | or |
448 | .BR super-minor . | |
449 | ||
450 | The | |
451 | .B sparc2.2 | |
452 | option will adjust the superblock of an array what was created on a Sparc | |
453 | machine running a patched 2.2 Linux kernel. This kernel got the | |
454 | alignment of part of the superblock wrong. You can use the | |
455 | .B "--examine --sparc2.2" | |
456 | option to | |
457 | .I mdadm | |
458 | to see what effect this would have. | |
459 | ||
460 | The | |
461 | .B super-minor | |
462 | option will update the | |
463 | .B "prefered minor" | |
464 | field on each superblock to match the minor number of the array being | |
feb716e9 | 465 | assembled. This is not needed on 2.6 and later kernels as they make |
5787fa49 NB |
466 | this adjustment automatically. |
467 | ||
e5329c37 NB |
468 | The |
469 | .B resync | |
470 | option will cause the array to be marked | |
471 | .I dirty | |
472 | meaning that any redundancy in the array (e.g. parity for raid5, | |
473 | copies for raid1) may be incorrect. This will cause the raid system | |
474 | to perform a "resync" pass to make sure that all redundant information | |
475 | is correct. | |
476 | ||
feb716e9 NB |
477 | The |
478 | .B summaries | |
479 | option will correct the summaries in the superblock. That is the | |
480 | counts of total, working, active, failed, and spare devices. | |
5787fa49 | 481 | |
e0d19036 | 482 | .SH For Manage mode: |
52826846 | 483 | |
cd29a5c8 NB |
484 | .TP |
485 | .BR -a ", " --add | |
486 | '''add, or | |
487 | hotadd listed devices. | |
52826846 | 488 | |
cd29a5c8 NB |
489 | .TP |
490 | .BR -r ", " --remove | |
2d465520 | 491 | remove listed devices. They must not be active. i.e. they should |
cd29a5c8 | 492 | be failed or spare devices. |
52826846 | 493 | |
cd29a5c8 NB |
494 | .TP |
495 | .BR -f ", " --fail | |
496 | mark listed devices as faulty. | |
52826846 | 497 | |
cd29a5c8 NB |
498 | .TP |
499 | .BR --set-faulty | |
500 | same as --fail. | |
52826846 | 501 | |
5787fa49 NB |
502 | .SH For Examine mode: |
503 | ||
504 | .TP | |
505 | .B --sparc2.2 | |
506 | In an array was created on a 2.2 Linux kernel patched with RAID | |
507 | support, the superblock will have been created incorrectly, or at | |
508 | least incompatibly with 2.4 and later kernels. Using the | |
509 | .B --sparc2.2 | |
510 | flag with | |
511 | .B --examine | |
512 | will fix the superblock before displaying it. If this appears to do | |
513 | the right thing, then the array can be successfully assembled using | |
514 | .BR "--assemble --update=sparc2.2" . | |
515 | ||
e0d19036 NB |
516 | .SH For Misc mode: |
517 | ||
cd29a5c8 NB |
518 | .TP |
519 | .BR -R ", " --run | |
520 | start a partially built array. | |
52826846 | 521 | |
cd29a5c8 NB |
522 | .TP |
523 | .BR -S ", " --stop | |
524 | deactivate array, releasing all resources. | |
52826846 | 525 | |
cd29a5c8 NB |
526 | .TP |
527 | .BR -o ", " --readonly | |
528 | mark array as readonly. | |
52826846 | 529 | |
cd29a5c8 NB |
530 | .TP |
531 | .BR -w ", " --readwrite | |
532 | mark array as readwrite. | |
52826846 | 533 | |
e0d19036 NB |
534 | .TP |
535 | .B --zero-superblock | |
536 | If the device contains a valid md superblock, the block is | |
537 | over-written with zeros. With | |
538 | --force | |
539 | the block where the superblock would be is over-written even if it | |
540 | doesn't appear to be valid. | |
52826846 | 541 | |
feb716e9 NB |
542 | .TP |
543 | .BR -t ", " --test | |
544 | When used with | |
545 | .BR --detail , | |
546 | the exit status of | |
547 | .I mdadm | |
548 | is set to reflect the status of the device. | |
549 | ||
e0d19036 NB |
550 | .SH For Monitor mode: |
551 | .TP | |
552 | .BR -m ", " --mail | |
553 | Give a mail address to send alerts to. | |
554 | ||
555 | .TP | |
556 | .BR -p ", " --program ", " --alert | |
557 | Give a program to be run whenever an event is detected. | |
558 | ||
559 | .TP | |
560 | .BR -d ", " --delay | |
561 | Give a delay in seconds. | |
562 | .B mdadm | |
563 | polls the md arrays and then waits this many seconds before polling | |
564 | again. The default is 60 seconds. | |
565 | ||
d013a55e NB |
566 | .TP |
567 | .BR -f ", " --daemonise | |
568 | Tell | |
569 | .B mdadm | |
570 | to run as a background daemon if it decides to monitor anything. This | |
571 | causes it to fork and run in the child, and to disconnect form the | |
572 | terminal. The process id of the child is written to stdout. | |
573 | This is useful with | |
574 | .B --scan | |
575 | which will only continue monitoring if a mail address or alert program | |
576 | is found in the config file. | |
577 | ||
b5e64645 NB |
578 | .TP |
579 | .BR -i ", " --pid-file | |
580 | When | |
581 | .B mdadm | |
582 | is running in daemon mode, write the pid of the daemon process to | |
583 | the specified file, instead of printing it on standard output. | |
584 | ||
aa88f531 NB |
585 | .TP |
586 | .BR -1 ", " --oneshot | |
587 | Check arrays only once. This will generate | |
588 | .B NewArray | |
589 | events and more significantly | |
590 | .B DegradedArray | |
591 | events. Running | |
592 | .in +5 | |
593 | .B " mdadm --monitor --scan -1" | |
594 | .in -5 | |
595 | from a cron script will ensure regular notification of any degraded arrays. | |
596 | ||
98c6faba NB |
597 | .TP |
598 | .BR -t ", " --test | |
599 | Generate a | |
600 | .B TestMessage | |
601 | alert for every array found at startup. This alert gets mailed and | |
602 | passed to the alert program. This can be used for testing that alert | |
603 | message to get through successfully. | |
604 | ||
e0d19036 | 605 | .SH ASSEMBLE MODE |
52826846 | 606 | |
cd29a5c8 NB |
607 | .HP 12 |
608 | Usage: | |
9a9dab36 | 609 | .B mdadm --assemble |
5787fa49 NB |
610 | .I md-device options-and-component-devices... |
611 | .HP 12 | |
612 | Usage: | |
613 | .B mdadm --assemble --scan | |
614 | .I md-devices-and-options... | |
cd29a5c8 NB |
615 | .HP 12 |
616 | Usage: | |
9a9dab36 | 617 | .B mdadm --assemble --scan |
cd29a5c8 | 618 | .I options... |
52826846 | 619 | |
cd29a5c8 | 620 | .PP |
52826846 | 621 | This usage assembles one or more raid arrays from pre-existing components. |
9a9dab36 | 622 | For each array, mdadm needs to know the md device, the identity of the |
e0d19036 | 623 | array, and a number of component-devices. These can be found in a number of ways. |
52826846 | 624 | |
5787fa49 NB |
625 | In the first usage example (without the |
626 | .BR --scan ) | |
627 | the first device given is the md device. | |
628 | In the second usage example, all devices listed are treated as md | |
629 | devices and assembly is attempted. | |
630 | In the third (where no devices are listed) all md devices that are | |
631 | listed in the configuration file are assembled. | |
52826846 | 632 | |
d013a55e NB |
633 | If precisely one device is listed, but |
634 | .B --scan | |
dd0781e5 | 635 | is not given, then |
d013a55e NB |
636 | .I mdadm |
637 | acts as though | |
638 | .B --scan | |
639 | was given and identify information is extracted from the configuration file. | |
640 | ||
cd29a5c8 | 641 | The identity can be given with the |
52826846 | 642 | .B --uuid |
cd29a5c8 NB |
643 | option, with the |
644 | .B --super-minor | |
5787fa49 | 645 | option, can be found in the config file, or will be taken from the |
e0d19036 | 646 | super block on the first component-device listed on the command line. |
52826846 NB |
647 | |
648 | Devices can be given on the | |
649 | .B --assemble | |
5787fa49 NB |
650 | command line or in the config file. Only devices which have an md |
651 | superblock which contains the right identity will be considered for | |
652 | any array. | |
52826846 NB |
653 | |
654 | The config file is only used if explicitly named with | |
655 | .B --config | |
d013a55e | 656 | or requested with (a possibly implicit) |
52826846 NB |
657 | .B --scan. |
658 | In the later case, | |
9a9dab36 | 659 | .B /etc/mdadm.conf |
52826846 NB |
660 | is used. |
661 | ||
662 | If | |
663 | .B --scan | |
cd29a5c8 NB |
664 | is not given, then the config file will only be used to find the |
665 | identity of md arrays. | |
52826846 | 666 | |
2d465520 | 667 | Normally the array will be started after it is assembled. However if |
cd29a5c8 | 668 | .B --scan |
2d465520 | 669 | is not given and insufficient drives were listed to start a complete |
cd29a5c8 NB |
670 | (non-degraded) array, then the array is not started (to guard against |
671 | usage errors). To insist that the array be started in this case (as | |
98c6faba | 672 | may work for RAID1, 4, 5 or 6), give the |
cd29a5c8 NB |
673 | .B --run |
674 | flag. | |
52826846 | 675 | |
dd0781e5 NB |
676 | If an |
677 | .B auto | |
678 | option is given, either on the command line (--auto) or in the | |
679 | configuration file (e.g. auto=part), then | |
680 | .I mdadm | |
681 | will create the md device if necessary or will re-create it if it | |
682 | doesn't look usable as it is. | |
683 | ||
684 | This can be useful for handling partitioned devices (which don't have | |
685 | a stable device number - it can change after a reboot) and when using | |
686 | "udev" to manage your | |
687 | .B /dev | |
688 | tree (udev cannot handle md devices because of the unusual device | |
689 | initialisation conventions). | |
690 | ||
691 | If the option to "auto" is "mdp" or "part" or (on the command line | |
692 | only) "p", then mdadm will create a partitionable array, using the | |
693 | first free one that is not inuse, and does not already have an entry | |
694 | in /dev (apart from numeric /dev/md* entries). | |
695 | ||
696 | If the option to "auto" is "yes" or "md" or (on the command line) | |
697 | nothing, then mdadm will create a traditional, non-partitionable md | |
698 | array. | |
699 | ||
700 | It is expected that the "auto" functionality will be used to create | |
701 | device entries with meaningful names such as "/dev/md/home" or | |
702 | "/dev/md/root", rather than names based on the numerical array number. | |
703 | ||
704 | When using this option to create a partitionable array, the device | |
705 | files for the first 4 partitions are also created. If a different | |
706 | number is required it can be simply appended to the auto option. | |
707 | e.g. "auto=part8". Partition names are created by appending a digit | |
708 | string to the device name, with an intervening "_p" if the device name | |
709 | ends with a digit. | |
710 | ||
711 | The | |
712 | .B --auto | |
713 | option is also available in Build and Create modes. As those modes do | |
714 | not use a config file, the "auto=" config option does not apply to | |
715 | these modes. | |
52826846 | 716 | |
cd29a5c8 | 717 | .SH BUILD MODE |
52826846 | 718 | |
cd29a5c8 NB |
719 | .HP 12 |
720 | Usage: | |
9a9dab36 | 721 | .B mdadm --build |
cd29a5c8 NB |
722 | .I device |
723 | .BI --chunk= X | |
724 | .BI --level= Y | |
b83d95f3 | 725 | .BI --raid-devices= Z |
cd29a5c8 NB |
726 | .I devices |
727 | ||
728 | .PP | |
52826846 | 729 | This usage is similar to |
cd29a5c8 | 730 | .BR --create . |
52826846 | 731 | The difference is that it creates a legacy array without a superblock. With |
cd29a5c8 | 732 | these arrays there is no difference between initially creating the array and |
52826846 NB |
733 | subsequently assembling the array, except that hopefully there is useful |
734 | data there in the second case. | |
735 | ||
cd29a5c8 NB |
736 | The level may only be 0, raid0, or linear. All devices must be listed |
737 | and the array will be started once complete. | |
738 | ||
739 | .SH CREATE MODE | |
740 | ||
741 | .HP 12 | |
742 | Usage: | |
9a9dab36 | 743 | .B mdadm --create |
cd29a5c8 NB |
744 | .I device |
745 | .BI --chunk= X | |
746 | .BI --level= Y | |
747 | .br | |
b83d95f3 | 748 | .BI --raid-devices= Z |
cd29a5c8 NB |
749 | .I devices |
750 | ||
751 | .PP | |
752 | This usage will initialise a new md array, associate some devices with | |
753 | it, and activate the array. | |
754 | ||
dd0781e5 NB |
755 | This the |
756 | .B --auto | |
757 | option is given (as described in more detail in the section on | |
758 | Assemble mode), then the md device will be created with a suitable | |
759 | device number if necessary. | |
760 | ||
cd29a5c8 | 761 | As devices are added, they are checked to see if they contain raid |
2d465520 | 762 | superblocks or filesystems. They are also checked to see if the variance in |
cd29a5c8 NB |
763 | device size exceeds 1%. |
764 | ||
765 | If any discrepancy is found, the array will not automatically be run, though | |
766 | the presence of a | |
767 | .B --run | |
768 | can override this caution. | |
769 | ||
2d465520 | 770 | To create a "degraded" array in which some devices are missing, simply |
d013a55e | 771 | give the word "\fBmissing\fP" |
2d465520 NB |
772 | in place of a device name. This will cause |
773 | .B mdadm | |
774 | to leave the corresponding slot in the array empty. | |
775 | For a RAID4 or RAID5 array at most one slot can be | |
98c6faba | 776 | "\fBmissing\fP"; for a RAID6 array at most two slots. |
2d465520 NB |
777 | For a RAID1 array, only one real device needs to be given. All of the |
778 | others can be | |
d013a55e | 779 | "\fBmissing\fP". |
2d465520 | 780 | |
feb716e9 NB |
781 | When creating a RAID5 array, |
782 | .B mdadm | |
783 | will automatically create a degraded array with an extra spare drive. | |
784 | This is because building the spare into a degraded array is in general faster than resyncing | |
785 | the parity on a non-degraded, but not clean, array. This feature can | |
786 | be over-ridden with the | |
b5e64645 | 787 | .I --force |
feb716e9 NB |
788 | option. |
789 | ||
cd29a5c8 NB |
790 | '''If the |
791 | '''.B --size | |
e0d19036 | 792 | '''option is given, it is not necessary to list any component-devices in this command. |
cd29a5c8 NB |
793 | '''They can be added later, before a |
794 | '''.B --run. | |
795 | '''If no | |
796 | '''.B --size | |
797 | '''is given, the apparent size of the smallest drive given is used. | |
798 | ||
799 | The General Management options that are valid with --create are: | |
800 | .TP | |
801 | .B --run | |
dd0781e5 | 802 | insist on running the array even if some devices look like they might |
cd29a5c8 NB |
803 | be in use. |
804 | ||
805 | .TP | |
806 | .B --readonly | |
807 | start the array readonly - not supported yet. | |
52826846 | 808 | |
e0d19036 | 809 | .SH MANAGE MODE |
cd29a5c8 NB |
810 | .HP 12 |
811 | Usage: | |
e0d19036 NB |
812 | .B mdadm |
813 | .I device | |
814 | .I options... devices... | |
cd29a5c8 NB |
815 | .PP |
816 | ||
e0d19036 NB |
817 | This usage will allow individual devices in an array to be failed, |
818 | removed or added. It is possible to perform multiple operations with | |
819 | on command. For example: | |
820 | .br | |
5787fa49 | 821 | .B " mdadm /dev/md0 -f /dev/hda1 -r /dev/hda1 -a /dev/hda1" |
e0d19036 NB |
822 | .br |
823 | will firstly mark | |
824 | .B /dev/hda1 | |
825 | as faulty in | |
826 | .B /dev/md0 | |
827 | and will then remove it from the array and finally add it back | |
2d465520 | 828 | in as a spare. However only one md array can be affected by a single |
e0d19036 NB |
829 | command. |
830 | ||
831 | .SH MISC MODE | |
832 | .HP 12 | |
833 | Usage: | |
9a9dab36 | 834 | .B mdadm |
e0d19036 NB |
835 | .I options ... |
836 | .I devices ... | |
837 | .PP | |
cd29a5c8 | 838 | |
b5e64645 | 839 | MISC mode includes a number of distinct operations that |
e0d19036 NB |
840 | operate on distinct devices. The operations are: |
841 | .TP | |
842 | --query | |
843 | The device is examined to see if it is | |
844 | (1) an active md array, or | |
845 | (2) a component of an md array. | |
846 | The information discovered is reported. | |
847 | ||
848 | .TP | |
849 | --detail | |
2d465520 NB |
850 | The device should be an active md device. |
851 | .B mdadm | |
852 | will display a detailed description of the array. | |
cd29a5c8 | 853 | .B --brief |
2d465520 NB |
854 | or |
855 | .B --scan | |
856 | will cause the output to be less detailed and the format to be | |
e0d19036 | 857 | suitable for inclusion in |
9a9dab36 | 858 | .BR /etc/mdadm.conf . |
feb716e9 NB |
859 | The exit status of |
860 | .I mdadm | |
861 | will normally be 0 unless | |
862 | .I mdadm | |
863 | failed to get useful information about the device(s). However if the | |
864 | .B --test | |
865 | option is given, then the exit status will be: | |
866 | .RS | |
867 | .TP | |
868 | 0 | |
869 | The array is functioning normally. | |
870 | .TP | |
871 | 1 | |
872 | The array has at least one failed device. | |
873 | .TP | |
874 | 2 | |
875 | The array has multiple failed devices and hence is unusable (raid4 or | |
876 | raid5). | |
877 | .TP | |
878 | 4 | |
879 | There was an error while trying to get information about the device. | |
880 | .RE | |
cd29a5c8 | 881 | |
e0d19036 NB |
882 | .TP |
883 | --examine | |
2d465520 NB |
884 | The device should be a component of an md array. |
885 | .B mdadm | |
886 | will read the md superblock of the device and display the contents. | |
e0d19036 NB |
887 | If |
888 | .B --brief | |
889 | is given, or | |
890 | .B --scan | |
891 | then multiple devices that are components of the one array | |
892 | are grouped together and reported in a single entry suitable | |
893 | for inclusion in | |
894 | .BR /etc/mdadm.conf . | |
895 | ||
2d465520 | 896 | Having |
e0d19036 NB |
897 | .B --scan |
898 | without listing any devices will cause all devices listed in the | |
899 | config file to be examined. | |
900 | ||
901 | .TP | |
902 | --stop | |
98c6faba NB |
903 | The devices should be active md arrays which will be deactivated, as |
904 | long as they are not currently in use. | |
e0d19036 NB |
905 | |
906 | .TP | |
907 | --run | |
908 | This will fully activate a partially assembled md array. | |
909 | ||
910 | .TP | |
911 | --readonly | |
912 | This will mark an active array as read-only, providing that it is | |
913 | not currently being used. | |
914 | ||
915 | .TP | |
916 | --readwrite | |
917 | This will change a | |
918 | .B readonly | |
919 | array back to being read/write. | |
920 | ||
2d465520 NB |
921 | .TP |
922 | --scan | |
923 | For all operations except | |
924 | .BR --examine , | |
925 | .B --scan | |
926 | will cause the operation to be applied to all arrays listed in | |
927 | .BR /proc/mdstat . | |
928 | For | |
929 | .BR --examine, | |
930 | .B --scan | |
931 | causes all devices listed in the config file to be examined. | |
932 | ||
933 | ||
e0d19036 NB |
934 | .SH MONITOR MODE |
935 | ||
cd29a5c8 NB |
936 | .HP 12 |
937 | Usage: | |
e0d19036 NB |
938 | .B mdadm --monitor |
939 | .I options... devices... | |
940 | ||
cd29a5c8 | 941 | .PP |
e0d19036 NB |
942 | This usage causes |
943 | .B mdadm | |
944 | to periodically poll a number of md arrays and to report on any events | |
945 | noticed. | |
946 | .B mdadm | |
947 | will never exit once it decides that there are arrays to be checked, | |
948 | so it should normally be run in the background. | |
949 | ||
2d465520 NB |
950 | As well as reporting events, |
951 | .B mdadm | |
952 | may move a spare drive from one array to another if they are in the | |
953 | same | |
954 | .B spare-group | |
955 | and if the destination array has a failed drive but not spares. | |
956 | ||
e0d19036 NB |
957 | If any devices are listed on the command line, |
958 | .B mdadm | |
959 | will only monitor those devices. Otherwise all arrays listed in the | |
960 | configuration file will be monitored. Further, if | |
961 | .B --scan | |
962 | is given, then any other md devices that appear in | |
963 | .B /proc/mdstat | |
964 | will also be monitored. | |
965 | ||
966 | The result of monitoring the arrays is the generation of events. | |
bd526cee | 967 | These events are passed to a separate program (if specified) and may |
2d465520 | 968 | be mailed to a given E-mail address. |
e0d19036 | 969 | |
bd526cee NB |
970 | When passing event to program, the program is run once for each event |
971 | and is given 2 or 3 command-line arguements. The first is the | |
972 | name of the event (see below). The second is the name of the | |
973 | md device which is affected, and the third is the name of a related | |
974 | device if relevant, such as a component device that has failed. | |
cd29a5c8 NB |
975 | |
976 | If | |
977 | .B --scan | |
e0d19036 NB |
978 | is given, then a program or an E-mail address must be specified on the |
979 | command line or in the config file. If neither are available, then | |
980 | .B mdadm | |
981 | will not monitor anything. | |
982 | Without | |
cd29a5c8 | 983 | .B --scan |
e0d19036 | 984 | .B mdadm |
2d465520 | 985 | will continue monitoring as long as something was found to monitor. If |
e0d19036 NB |
986 | no program or email is given, then each event is reported to |
987 | .BR stdout . | |
cd29a5c8 | 988 | |
e0d19036 NB |
989 | The different events are: |
990 | ||
991 | .RS 4 | |
992 | .TP | |
993 | .B DeviceDisappeared | |
2d465520 | 994 | An md array which previously was configured appears to no longer be |
e0d19036 NB |
995 | configured. |
996 | ||
997 | .TP | |
998 | .B RebuildStarted | |
999 | An md array started reconstruction. | |
1000 | ||
1001 | .TP | |
1002 | .BI Rebuild NN | |
1003 | Where | |
1004 | .I NN | |
1005 | is 20, 40, 60, or 80, this indicates that rebuild has passed that many | |
1006 | percentage of the total. | |
1007 | ||
98c6faba NB |
1008 | .TP |
1009 | .B RebuildFinished | |
1010 | An md array that was rebuilding, isn't any more, either because it | |
1011 | finished normally or was aborted. | |
1012 | ||
e0d19036 NB |
1013 | .TP |
1014 | .B Fail | |
1015 | An active component device of an array has been marked as faulty. | |
1016 | ||
1017 | .TP | |
1018 | .B FailSpare | |
1019 | A spare component device which was being rebuilt to replace a faulty | |
1020 | device has failed. | |
1021 | ||
1022 | .TP | |
1023 | .B SpareActive | |
1024 | A spare component device which was being rebuilt to replace a faulty | |
1025 | device as been successfully rebuild and has been made active. | |
1026 | ||
1027 | .TP | |
1028 | .B NewArray | |
1029 | A new md array has been detected in the | |
1030 | .B /proc/mdstat | |
1031 | file. | |
1032 | ||
aa88f531 NB |
1033 | .TP |
1034 | .B DegradedArray | |
1035 | A newly noticed array appears to be degraded. This message is not | |
1036 | generated when | |
1037 | .I mdadm | |
1038 | notices a drive failure which causes degradation, but only when | |
1039 | .I mdadm | |
1040 | notices that an array is degraded when it first sees the array. | |
1041 | ||
e0d19036 NB |
1042 | .TP |
1043 | .B MoveSpare | |
1044 | A spare drive has been moved from one array in a | |
1045 | .B spare-group | |
1046 | to another to allow a failed drive to be replaced. | |
1047 | ||
98c6faba NB |
1048 | .TP |
1049 | .B TestMessage | |
1050 | An array was found at startup, and the | |
1051 | .B --test | |
1052 | flag was given. | |
e0d19036 NB |
1053 | .RE |
1054 | ||
1055 | Only | |
98c6faba NB |
1056 | .B Fail , |
1057 | .B FailSpare , | |
1058 | .B DegradedArray , | |
e0d19036 | 1059 | and |
98c6faba | 1060 | .B TestMessage |
e0d19036 NB |
1061 | cause Email to be sent. All events cause the program to be run. |
1062 | The program is run with two or three arguments, they being the event | |
1063 | name, the array device and possibly a second device. | |
1064 | ||
1065 | Each event has an associated array device (e.g. | |
1066 | .BR /dev/md1 ) | |
1067 | and possibly a second device. For | |
1068 | .BR Fail , | |
1069 | .BR FailSpare , | |
1070 | and | |
1071 | .B SpareActive | |
1072 | the second device is the relevant component device. | |
1073 | For | |
1074 | .B MoveSpare | |
1075 | the second device is the array that the spare was moved from. | |
1076 | ||
1077 | For | |
1078 | .B mdadm | |
1079 | to move spares from one array to another, the different arrays need to | |
1080 | be labelled with the same | |
1081 | .B spare-group | |
1082 | in the configuration file. The | |
1083 | .B spare-group | |
1084 | name can be any string. It is only necessary that different spare | |
2d465520 | 1085 | groups use different names. |
e0d19036 NB |
1086 | |
1087 | When | |
9a9dab36 | 1088 | .B mdadm |
e0d19036 NB |
1089 | detects that an array which is in a spare group has fewer active |
1090 | devices than necessary for the complete array, and has no spare | |
1091 | devices, it will look for another array in the same spare group that | |
1092 | has a full complement of working drive and a spare. It will then | |
1093 | attempt to remove the spare from the second drive and add it to the | |
1094 | first. | |
1095 | If the removal succeeds but the adding fails, then it is added back to | |
1096 | the original array. | |
1097 | ||
dd0781e5 NB |
1098 | .SH GROW MODE |
1099 | The GROW mode is used for changing the size or shape of an active | |
1100 | array. | |
1101 | For this to work, the kernel must support the necessary change. | |
1102 | Various types of growth may be added during 2.6 development, possibly | |
1103 | including restructuring a raid5 array to have more active devices. | |
1104 | ||
1105 | Currently the only support available is to change the "size" attribute | |
1106 | for arrays with redundancy, and the raid-disks attribute of RAID1 | |
1107 | arrays. | |
1108 | ||
1109 | Normally when an array is build the "size" it taken from the smallest | |
1110 | of the drives. If all the small drives in an arrays are, one at a | |
1111 | time, removed and replaced with larger drives, then you could have an | |
1112 | array of large drives with only a small amount used. In this | |
1113 | situation, changing the "size" with "GROW" mode will allow the extra | |
1114 | space to start being used. If the size is increased in this way, a | |
1115 | "resync" process will start to make sure the new parts of the array | |
1116 | are synchronised. | |
1117 | ||
1118 | Note that when an array changes size, any filesystem that may be | |
1119 | stored in the array will not automatically grow to use the space. The | |
1120 | filesystem will need to be explicitly told to use the extra space. | |
1121 | ||
1122 | A RAID1 array can work with any number of devices from 1 upwards | |
1123 | (though 1 is not very useful). There may be times which you want to | |
1124 | increase or decrease the number of active devices. Note that this is | |
1125 | different to hot-add or hot-remove which changes the number of | |
1126 | inactive devices. | |
1127 | ||
1128 | When reducing the number of devices in a RAID1 array, the slots which | |
1129 | are to be removed from the array must already be vacant. That is, the | |
1130 | devices that which were in those slots must be failed and removed. | |
1131 | ||
1132 | When the number of devices is increased, any hot spares that are | |
1133 | present may be activated immediately. | |
1134 | ||
2d465520 NB |
1135 | .SH EXAMPLES |
1136 | ||
5787fa49 | 1137 | .B " mdadm --query /dev/name-of-device" |
2d465520 | 1138 | .br |
5787fa49 NB |
1139 | This will find out if a given device is a raid array, or is part of |
1140 | one, and will provide brief information about the device. | |
2d465520 | 1141 | |
5787fa49 | 1142 | .B " mdadm --assemble --scan" |
2d465520 | 1143 | .br |
5787fa49 NB |
1144 | This will assemble and start all arrays listed in the standard confile |
1145 | file. This command will typically go in a system startup file. | |
2d465520 | 1146 | |
2d465520 | 1147 | .B " mdadm --stop --scan" |
5787fa49 NB |
1148 | .br |
1149 | This will shut down all array that can be shut down (i.e. are not | |
19f8b8fc | 1150 | currently in use). This will typically go in a system shutdown script. |
2d465520 | 1151 | |
5787fa49 | 1152 | .B " mdadm --follow --scan --delay=120" |
2d465520 | 1153 | .br |
5787fa49 NB |
1154 | If (and only if) there is an Email address or program given in the |
1155 | standard config file, then | |
1156 | monitor the status of all arrays listed in that file by | |
1157 | polling them ever 2 minutes. | |
2d465520 | 1158 | |
5787fa49 | 1159 | .B " mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/hd[ac]1" |
2d465520 | 1160 | .br |
5787fa49 | 1161 | Create /dev/md0 as a RAID1 array consisting of /dev/hda1 and /dev/hdc1. |
2d465520 | 1162 | |
2d465520 NB |
1163 | .br |
1164 | .B " echo 'DEVICE /dev/hd*[0-9] /dev/sd*[0-9]' > mdadm.conf" | |
1165 | .br | |
1166 | .B " mdadm --detail --scan >> mdadm.conf" | |
1167 | .br | |
5787fa49 NB |
1168 | This will create a prototype config file that describes currently |
1169 | active arrays that are known to be made from partitions of IDE or SCSI drives. | |
2d465520 NB |
1170 | This file should be reviewed before being used as it may |
1171 | contain unwanted detail. | |
1172 | ||
2d465520 NB |
1173 | .B " echo 'DEVICE /dev/hd[a-z] /dev/sd*[a-z]' > mdadm.conf" |
1174 | .br | |
5787fa49 NB |
1175 | .B " mdadm --examine --scan --config=mdadm.conf >> mdadm.conf" |
1176 | .ber | |
1177 | This will find what arrays could be assembled from existign IDE and | |
1178 | SCSI whole drives (not partitions) and store the information is the | |
1179 | format of a config file. | |
2d465520 NB |
1180 | This file is very likely to contain unwanted detail, particularly |
1181 | the | |
1182 | .B devices= | |
5787fa49 NB |
1183 | entries. It should be reviewed and edited before being used as an |
1184 | actual config file. | |
2d465520 | 1185 | |
5787fa49 | 1186 | .B " mdadm --examine --brief --scan --config=partitions" |
2d465520 | 1187 | .br |
5787fa49 NB |
1188 | .B " mdadm -Ebsc partitions" |
1189 | .br | |
1190 | Create a list of devices by reading | |
1191 | .BR /proc/partitions , | |
1192 | scan these for RAID superblocks, and printout a brief listing of all | |
1193 | that was found. | |
2d465520 | 1194 | |
5787fa49 | 1195 | .B " mdadm -Ac partitions -m 0 /dev/md0" |
2d465520 | 1196 | .br |
5787fa49 NB |
1197 | Scan all partitions and devices listed in |
1198 | .BR /proc/partitions | |
1199 | and assemble | |
1200 | .B /dev/md0 | |
1201 | out of all such devices with a RAID superblock with a minor number of 0. | |
2d465520 | 1202 | |
d013a55e NB |
1203 | .B " mdadm --monitor --scan --daemonise > /var/run/mdadm" |
1204 | .br | |
1205 | If config file contains a mail address or alert program, run mdadm in | |
1206 | the background in monitor mode monitoring all md devices. Also write | |
1207 | pid of mdadm daemon to | |
1208 | .BR /var/run/mdadm . | |
1209 | ||
5787fa49 | 1210 | .B " mdadm --create --help" |
2d465520 | 1211 | .br |
5787fa49 | 1212 | Providew help about the Create mode. |
2d465520 | 1213 | |
5787fa49 NB |
1214 | .B " mdadm --config --help" |
1215 | .br | |
1216 | Provide help about the format of the config file. | |
2d465520 | 1217 | |
5787fa49 NB |
1218 | .B " mdadm --help" |
1219 | .br | |
1220 | Provide general help. | |
cd29a5c8 | 1221 | |
cd29a5c8 NB |
1222 | |
1223 | .SH FILES | |
1224 | ||
1225 | .SS /proc/mdstat | |
1226 | ||
1227 | If you're using the | |
1228 | .B /proc | |
1229 | filesystem, | |
1230 | .B /proc/mdstat | |
2d465520 NB |
1231 | lists all active md devices with information about them. |
1232 | .B mdadm | |
1233 | uses this to find arrays when | |
1234 | .B --scan | |
1235 | is given in Misc mode, and to monitor array reconstruction | |
1236 | on Monitor mode. | |
1237 | ||
cd29a5c8 | 1238 | |
9a9dab36 | 1239 | .SS /etc/mdadm.conf |
cd29a5c8 | 1240 | |
11a3e71d NB |
1241 | The config file lists which devices may be scanned to see if |
1242 | they contain MD super block, and gives identifying information | |
1243 | (e.g. UUID) about known MD arrays. See | |
1244 | .BR mdadm.conf (5) | |
1245 | for more details. | |
cd29a5c8 | 1246 | |
52826846 | 1247 | |
2d465520 NB |
1248 | .SH NOTE |
1249 | .B mdadm | |
1250 | was previously known as | |
1251 | .BR mdctl . | |
1252 | ||
52826846 | 1253 | .SH SEE ALSO |
cd29a5c8 NB |
1254 | For information on the various levels of |
1255 | RAID, check out: | |
1256 | ||
1257 | .IP | |
1258 | .UR http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ | |
1259 | http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/ | |
1260 | .UE | |
1261 | .PP | |
1262 | for new releases of the RAID driver check out: | |
1263 | ||
1264 | .IP | |
1265 | .UR ftp://ftp.kernel.org/pub/linux/kernel/people/mingo/raid-patches | |
1266 | ftp://ftp.kernel.org/pub/linux/kernel/people/mingo/raid-patches | |
1267 | .UE | |
1268 | .PP | |
1269 | or | |
1270 | .IP | |
1271 | .UR http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/ | |
1272 | http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/ | |
1273 | .URk | |
1274 | .PP | |
56eb10c0 NB |
1275 | .BR mdadm.conf (5), |
1276 | .BR md (4). | |
1277 | .PP | |
52826846 NB |
1278 | .IR raidtab (5), |
1279 | .IR raid0run (8), | |
1280 | .IR raidstop (8), | |
1281 | .IR mkraid (8) |