]> git.ipfire.org Git - thirdparty/mdadm.git/blame - ReadMe.c
When assembly arrays using incomplete detail, prefer arrays built for this host.
[thirdparty/mdadm.git] / ReadMe.c
CommitLineData
64c4757e 1/*
9a9dab36 2 * mdadm - manage Linux "md" devices aka RAID arrays.
64c4757e 3 *
4f589ad0 4 * Copyright (C) 2001-2006 Neil Brown <neilb@suse.de>
64c4757e
NB
5 *
6 *
7 * This program is free software; you can redistribute it and/or modify
8 * it under the terms of the GNU General Public License as published by
9 * the Free Software Foundation; either version 2 of the License, or
10 * (at your option) any later version.
11 *
12 * This program is distributed in the hope that it will be useful,
13 * but WITHOUT ANY WARRANTY; without even the implied warranty of
14 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15 * GNU General Public License for more details.
16 *
17 * You should have received a copy of the GNU General Public License
18 * along with this program; if not, write to the Free Software
19 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
20 *
21 * Author: Neil Brown
22 * Email: <neilb@cse.unsw.edu.au>
23 * Paper: Neil Brown
24 * School of Computer Science and Engineering
25 * The University of New South Wales
26 * Sydney, 2052
27 * Australia
28 */
29
9a9dab36 30#include "mdadm.h"
64c4757e 31
90d0adf4 32char Version[] = Name " - v2.4.1 - 4 April 2006\n";
4b1ac34b 33
64c4757e
NB
34/*
35 * File: ReadMe.c
36 *
37 * This file contains general comments about the implementation
9a9dab36 38 * and the various usage messages that can be displayed by mdadm
64c4757e 39 *
9a9dab36 40 * mdadm is a single program that can be used to control Linux md devices.
64c4757e
NB
41 * It is intended to provide all the functionality of the mdtools and
42 * raidtools but with a very different interface.
9a9dab36 43 * mdadm can perform all functions without a configuration file.
64c4757e
NB
44 * There is the option of using a configuration file, but not in the same
45 * way that raidtools uses one
46 * raidtools uses a configuration file to describe how to create a RAID
47 * array, and also uses this file partially to start a previously
48 * created RAID array. Further, raidtools requires the configuration
49 * file for such things as stopping a raid array which needs to know
50 * nothing about the array.
51 *
9a9dab36 52 * The configuration file that can be used by mdadm lists two
64c4757e
NB
53 * different things:
54 * 1/ a mapping from uuid to md device to identify which arrays are
55 * expect and what names (numbers) they should be given
56 * 2/ a list of devices that should be scanned for md sub-devices
57 *
58 *
59 */
60
61/*
dd0781e5 62 * mdadm has 7 major modes of operation:
64c4757e 63 * 1/ Create
5787fa49 64 * This mode is used to create a new array with a superblock
64c4757e
NB
65 * It can progress in several step create-add-add-run
66 * or it can all happen with one command
67 * 2/ Assemble
68 * This mode is used to assemble the parts of a previously created
69 * array into an active array. Components can be explicitly given
9a9dab36 70 * or can be searched for. mdadm (optionally) check that the components
5787fa49 71 * do form a bona-fide array, and can, on request, fiddle superblock
64c4757e
NB
72 * version numbers so as to assemble a faulty array.
73 * 3/ Build
74 * This is for building legacy arrays without superblocks
75 * 4/ Manage
e0d19036
NB
76 * This is for doing something to one or more devices
77 * in an array, such as add,remove,fail.
78 * run/stop/readonly/readwrite are also available
79 * 5/ Misc
80 * This is for doing things to individual devices.
81 * They might be parts of an array so
82 * zero-superblock, examine might be appropriate
83 * They might be md arrays so
84 * run,stop,rw,ro,detail might be appropriate
85 * Also query will treat it as either
86 * 6/ Monitor
87 * This mode never exits but just monitors arrays and reports changes.
dd0781e5
NB
88 * 7/ Grow
89 * This mode allows for changing of key attributes of a raid array, such
90 * as size, number of devices, and possibly even layout.
91 * At the time if writing, there is only minimal support.
64c4757e
NB
92 */
93
773135f5
NB
94char short_options[]="-ABCDEFGQhVXvqbc:i:l:p:m:n:x:u:c:d:z:U:sarfRSow1tye:";
95char short_bitmap_auto_options[]="-ABCDEFGQhVXvqb:c:i:l:p:m:n:x:u:c:d:z:U:sa:rfRSow1tye:";
96
64c4757e
NB
97struct option long_options[] = {
98 {"manage", 0, 0, '@'},
e0d19036 99 {"misc", 0, 0, '#'},
64c4757e
NB
100 {"assemble", 0, 0, 'A'},
101 {"build", 0, 0, 'B'},
102 {"create", 0, 0, 'C'},
103 {"detail", 0, 0, 'D'},
104 {"examine", 0, 0, 'E'},
52826846 105 {"follow", 0, 0, 'F'},
dd0781e5 106 {"grow", 0, 0, 'G'},
e0d19036
NB
107 {"zero-superblock", 0, 0, 'K'}, /* deliberately no a short_option */
108 {"query", 0, 0, 'Q'},
c82f047c 109 {"examine-bitmap", 0, 0, 'X'},
52826846
NB
110
111 /* synonyms */
112 {"monitor", 0, 0, 'F'},
113
64c4757e
NB
114 /* after those will normally come the name of the md device */
115 {"help", 0, 0, 'h'},
56eedc1a 116 {"help-options",0,0,'h'},
64c4757e
NB
117 {"version", 0, 0, 'V'},
118 {"verbose", 0, 0, 'v'},
dab6685f 119 {"quiet", 0, 0, 'q'},
64c4757e
NB
120
121 /* For create or build: */
122 {"chunk", 1, 0, 'c'},
123 {"rounding", 1, 0, 'c'}, /* for linear, chunk is really a rounding number */
98c6faba 124 {"level", 1, 0, 'l'}, /* 0,1,4,5,6,linear */
5787fa49 125 {"parity", 1, 0, 'p'}, /* {left,right}-{a,}symmetric */
64c4757e
NB
126 {"layout", 1, 0, 'p'},
127 {"raid-disks",1, 0, 'n'},
b83d95f3 128 {"raid-devices",1, 0, 'n'},
64c4757e 129 {"spare-disks",1,0, 'x'},
b83d95f3 130 {"spare-devices",1,0, 'x'},
dd0781e5 131 {"size", 1, 0, 'z'},
c82f047c 132 {"auto", 1, 0, 'a'}, /* also for --assemble */
997aed5d 133 {"assume-clean",0,0, AssumeClean },
f9ce90ba 134 {"metadata", 1, 0, 'e'}, /* superblock format */
c82f047c 135 {"bitmap", 1, 0, 'b'},
997aed5d
NB
136 {"bitmap-chunk", 1, 0, BitmapChunk},
137 {"write-behind", 2, 0, WriteBehind},
dfd4d8ee 138 {"write-mostly",0, 0, 'W'},
997aed5d
NB
139 {"re-add", 0, 0, ReAdd},
140 {"homehost", 1, 0, HomeHost},
64c4757e
NB
141
142 /* For assemble */
143 {"uuid", 1, 0, 'u'},
52826846 144 {"super-minor",1,0, 'm'},
947fd4dd 145 {"name", 1, 0, 'N'},
64c4757e
NB
146 {"config", 1, 0, 'c'},
147 {"scan", 0, 0, 's'},
148 {"force", 0, 0, 'f'},
5787fa49 149 {"update", 1, 0, 'U'},
dfd4d8ee 150
64c4757e
NB
151 /* Management */
152 {"add", 0, 0, 'a'},
153 {"remove", 0, 0, 'r'},
154 {"fail", 0, 0, 'f'},
155 {"set-faulty",0, 0, 'f'},
156 {"run", 0, 0, 'R'},
157 {"stop", 0, 0, 'S'},
158 {"readonly", 0, 0, 'o'},
159 {"readwrite", 0, 0, 'w'},
997aed5d 160 {"no-degraded",0,0, NoDegraded },
52826846 161
cd29a5c8
NB
162 /* For Detail/Examine */
163 {"brief", 0, 0, 'b'},
997aed5d 164 {"sparc2.2", 0, 0, Sparc22},
feb716e9 165 {"test", 0, 0, 't'},
cd29a5c8 166
52826846
NB
167 /* For Follow/monitor */
168 {"mail", 1, 0, 'm'},
169 {"program", 1, 0, 'p'},
170 {"alert", 1, 0, 'p'},
171 {"delay", 1, 0, 'd'},
56eedc1a
NB
172 {"daemonise", 0, 0, 'f'},
173 {"daemonize", 0, 0, 'f'},
aa88f531 174 {"oneshot", 0, 0, '1'},
b5e64645 175 {"pid-file", 1, 0, 'i'},
06b0d786 176 /* For Grow */
997aed5d 177 {"backup-file", 1,0, BackupFile},
64c4757e
NB
178
179 {0, 0, 0, 0}
180};
181
182char Usage[] =
9a9dab36 183"Usage: mdadm --help\n"
64c4757e
NB
184" for help\n"
185;
186
187char Help[] =
e5a5d81e
NB
188"mdadm is used for building, managing, and monitoring\n"
189"Linux md devices (aka RAID arrays)\n"
9a9dab36 190"Usage: mdadm --create device options...\n"
e5a5d81e 191" Create a new array from unused devices.\n"
9a9dab36 192" mdadm --assemble device options...\n"
e968ba60 193" Assemble a previously created array.\n"
9a9dab36 194" mdadm --build device options...\n"
e5a5d81e 195" Create or assemble an array without metadata.\n"
e0d19036 196" mdadm --manage device options...\n"
e968ba60 197" make changes to an existing array.\n"
e0d19036 198" mdadm --misc options... devices\n"
e968ba60 199" report on or modify various md related devices.\n"
e0d19036 200" mdadm --monitor options...\n"
e968ba60 201" Monitor one or more array for significant changes.\n"
9a9dab36 202" mdadm device options...\n"
e968ba60 203" Shorthand for --manage.\n"
e5a5d81e
NB
204"Any parameter that does not start with '-' is treated as a device name\n"
205"or, for --examine-bitmap, a file name.\n"
206"The first such name is often the name of an md device. Subsequent\n"
207"names are often names of component devices.\n"
208"\n"
56eedc1a 209" For detailed help on the above major modes use --help after the mode\n"
e0d19036 210" e.g.\n"
9a9dab36 211" mdadm --assemble --help\n"
56eedc1a
NB
212" For general help on options use\n"
213" mdadm --help-options\n"
214;
215
216char OptionHelp[] =
64c4757e 217"Any parameter that does not start with '-' is treated as a device name\n"
c82f047c 218"or, for --examine-bitmap, a file name.\n"
e0d19036 219"The first such name is often the name of an md device. Subsequent\n"
e5a5d81e 220"names are often names of component devices.\n"
52826846 221"\n"
e0d19036 222"Some common options are:\n"
56eedc1a 223" --help -h : General help message or, after above option,\n"
64c4757e 224" mode specific help message\n"
56eedc1a 225" --help-options : This help message\n"
9a9dab36 226" --version -V : Print version information for mdadm\n"
64c4757e 227" --verbose -v : Be more verbose about what is happening\n"
dab6685f 228" --quiet -q : Don't print un-necessary messages\n"
e0d19036
NB
229" --brief -b : Be less verbose, more brief\n"
230" --force -f : Override normal checks and be more forceful\n"
231"\n"
232" --assemble -A : Assemble an array\n"
e5a5d81e 233" --build -B : Build an array without metadata\n"
e0d19036
NB
234" --create -C : Create a new array\n"
235" --detail -D : Display details of an array\n"
5787fa49 236" --examine -E : Examine superblock on an array component\n"
c82f047c 237" --examine-bitmap -X: Display the detail of a bitmap file\n"
e0d19036
NB
238" --monitor -F : monitor (follow) some arrays\n"
239" --query -Q : Display general information about how a\n"
240" device relates to the md driver\n"
241;
242/*
64c4757e
NB
243"\n"
244" For create or build:\n"
c82f047c 245" --bitmap= -b : File to store bitmap in - may pre-exist for --build\n"
64c4757e 246" --chunk= -c : chunk size of kibibytes\n"
5787fa49 247" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
248" --level= -l : raid level: 0,1,4,5,6,linear,mp. 0 or linear for build\n"
249" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
64c4757e 250" --layout= : same as --parity\n"
b83d95f3
NB
251" --raid-devices= -n : number of active devices in array\n"
252" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
e5329c37 253" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
52826846
NB
254" --force -f : Honour devices as listed on command line. Don't\n"
255" : insert a missing drive for RAID5.\n"
dd0781e5
NB
256" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
257" --assume-clean : Assume the array is already in-sync. This is dangerous.\n"
c82f047c
NB
258" --bitmap-chunk= : chunksize of bitmap in bitmap file (Kilobytes)\n"
259" --delay= -d : seconds between bitmap updates\n"
dfd4d8ee 260" --write-behind= : number of simultaneous write-behind requests to allow (requires bitmap)\n"
947fd4dd 261" --name= -N : Textual name for array - max 32 characters\n"
64c4757e
NB
262"\n"
263" For assemble:\n"
c82f047c 264" --bitmap= -b : File to find bitmap information in\n"
64c4757e
NB
265" --uuid= -u : uuid of array to assemble. Devices which don't\n"
266" have this uuid are excluded\n"
52826846
NB
267" --super-minor= -m : minor number to look for in super-block when\n"
268" choosing devices to use.\n"
947fd4dd 269" --name= -N : Array name to look for in super-block.\n"
64c4757e
NB
270" --config= -c : config file\n"
271" --scan -s : scan config file for missing information\n"
272" --force -f : Assemble the array even if some superblocks appear out-of-date\n"
feb716e9 273" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
dd0781e5 274" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
b8a8ccf9 275" --no-degraded : Do not start any degraded arrays - default unless --scan.\n"
64c4757e 276"\n"
cd29a5c8
NB
277" For detail or examine:\n"
278" --brief -b : Just print device name and UUID\n"
279"\n"
52826846
NB
280" For follow/monitor:\n"
281" --mail= -m : Address to mail alerts of failure to\n"
282" --program= -p : Program to run when an event is detected\n"
283" --alert= : same as --program\n"
284" --delay= -d : seconds of delay between polling state. default=60\n"
285"\n"
64c4757e
NB
286" General management:\n"
287" --add -a : add, or hotadd subsequent devices\n"
288" --remove -r : remove subsequent devices\n"
289" --fail -f : mark subsequent devices a faulty\n"
290" --set-faulty : same as --fail\n"
291" --run -R : start a partially built array\n"
5787fa49 292" --stop -S : deactivate array, releasing all resources\n"
64c4757e
NB
293" --readonly -o : mark array as readonly\n"
294" --readwrite -w : mark array as readwrite\n"
9a9dab36 295" --zero-superblock : erase the MD superblock from a device.\n"
64c4757e 296;
e0d19036 297*/
64c4757e
NB
298
299char Help_create[] =
b83d95f3 300"Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e 301"\n"
aa88f531
NB
302" This usage will initialise a new md array, associate some\n"
303" devices with it, and activate the array. In order to create an\n"
304" array with some devices missing, use the special word 'missing' in\n"
305" place of the relevant device name.\n"
64c4757e 306"\n"
aa88f531 307" Before devices are added, they are checked to see if they already contain\n"
e0d19036 308" raid superblocks or filesystems. They are also checked to see if\n"
64c4757e 309" the variance in device size exceeds 1%.\n"
aa88f531
NB
310" If any discrepancy is found, the user will be prompted for confirmation\n"
311" before the array is created. The presence of a '--run' can override this\n"
64c4757e
NB
312" caution.\n"
313"\n"
e0d19036
NB
314" If the --size option is given then only that many kilobytes of each\n"
315" device is used, no matter how big each device is.\n"
682c7051 316" If no --size is given, the apparent size of the smallest drive given\n"
e0d19036
NB
317" is used for raid level 1 and greater, and the full device is used for\n"
318" other levels.\n"
682c7051 319"\n"
e0d19036 320" Options that are valid with --create (-C) are:\n"
c82f047c 321" --bitmap= : Create a bitmap for the array with the given filename\n"
e0d19036 322" --chunk= -c : chunk size of kibibytes\n"
5787fa49 323" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
324" --level= -l : raid level: 0,1,4,5,6,linear,multipath and synonyms\n"
325" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
e0d19036 326" --layout= : same as --parity\n"
b83d95f3
NB
327" --raid-devices= -n : number of active devices in array\n"
328" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
e5329c37 329" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
e0d19036
NB
330" --force -f : Honour devices as listed on command line. Don't\n"
331" : insert a missing drive for RAID5.\n"
aa88f531 332" --run -R : insist of running the array even if not all\n"
e0d19036 333" : devices are present or some look odd.\n"
aa88f531 334" --readonly -o : start the array readonly - not supported yet.\n"
947fd4dd 335" --name= -N : Textual name for array - max 32 characters\n"
c82f047c
NB
336" --bitmap-chunk= : bitmap chunksize in Kilobytes.\n"
337" --delay= -d : bitmap update delay in seconds.\n"
64c4757e
NB
338"\n"
339;
340
341char Help_build[] =
b83d95f3 342"Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e
NB
343"\n"
344" This usage is similar to --create. The difference is that it creates\n"
e0d19036 345" a legacy array without a superblock. With these arrays there is no\n"
64c4757e
NB
346" different between initially creating the array and subsequently\n"
347" assembling the array, except that hopefully there is useful data\n"
348" there in the second case.\n"
349"\n"
e0d19036 350" The level may only be 0, raid0, or linear.\n"
64c4757e 351" All devices must be listed and the array will be started once complete.\n"
e0d19036 352" Options that are valid with --build (-B) are:\n"
c82f047c 353" --bitmap= : file to store/find bitmap information in.\n"
e0d19036 354" --chunk= -c : chunk size of kibibytes\n"
5787fa49 355" --rounding= : rounding factor for linear array (==chunk size)\n"
e0d19036 356" --level= -l : 0, raid0, or linear\n"
c82f047c
NB
357" --raid-devices= -n : number of active devices in array\n"
358" --bitmap-chunk= : bitmap chunksize in Kilobytes.\n"
359" --delay= -d : bitmap update delay in seconds.\n"
64c4757e
NB
360;
361
362char Help_assemble[] =
9a9dab36
NB
363"Usage: mdadm --assemble device options...\n"
364" mdadm --assemble --scan options...\n"
64c4757e
NB
365"\n"
366"This usage assembles one or more raid arrays from pre-existing\n"
367"components.\n"
e0d19036 368"For each array, mdadm needs to know the md device, the identity of\n"
52826846
NB
369"the array, and a number of sub devices. These can be found in a number\n"
370"of ways.\n"
371"\n"
372"The md device is either given on the command line or is found listed\n"
373"in the config file. The array identity is determined either from the\n"
e0d19036 374"--uuid or --super-minor commandline arguments, from the config file,\n"
52826846 375"or from the first component device on the command line.\n"
64c4757e 376"\n"
52826846
NB
377"The different combinations of these are as follows:\n"
378" If the --scan option is not given, then only devices and identities\n"
379" listed on the command line are considered.\n"
e0d19036 380" The first device will be the array device, and the remainder will be\n"
52826846
NB
381" examined when looking for components.\n"
382" If an explicit identity is given with --uuid or --super-minor, then\n"
e0d19036 383" only devices with a superblock which matches that identity is considered,\n"
52826846 384" otherwise every device listed is considered.\n"
64c4757e 385"\n"
52826846
NB
386" If the --scan option is given, and no devices are listed, then\n"
387" every array listed in the config file is considered for assembly.\n"
e0d19036 388" The identity of candidate devices are determined from the config file.\n"
64c4757e 389"\n"
52826846
NB
390" If the --scan option is given as well as one or more devices, then\n"
391" Those devices are md devices that are to be assembled. Their identity\n"
392" and components are determined from the config file.\n"
64c4757e 393"\n"
b8a8ccf9
NB
394" If mdadm can not find all of the components for an array, it will assemble\n"
395" it but not activate it unless --run or --scan is given. To preserve this\n"
396" behaviour even with --scan, add --no-degraded. Note that \"all of the\n"
397" components\" means as many as were present the last time the array was running\n"
398" as recorded in the superblock. If the array was already degraded, and\n"
399" the missing device is not a new problem, it will still be assembled. It\n"
400" is only newly missing devices that cause the array not to be started.\n"
401"\n"
e0d19036 402"Options that are valid with --assemble (-A) are:\n"
c82f047c 403" --bitmap= : bitmap file to use wit the array\n"
e0d19036
NB
404" --uuid= -u : uuid of array to assemble. Devices which don't\n"
405" have this uuid are excluded\n"
406" --super-minor= -m : minor number to look for in super-block when\n"
407" choosing devices to use.\n"
947fd4dd 408" --name= -N : Array name to look for in super-block.\n"
e0d19036
NB
409" --config= -c : config file\n"
410" --scan -s : scan config file for missing information\n"
411" --run -R : Try to start the array even if not enough devices\n"
412" for a full array are present\n"
413" --force -f : Assemble the array even if some superblocks appear\n"
414" : out-of-date. This involves modifying the superblocks.\n"
feb716e9 415" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
b8a8ccf9 416" --no-degraded : Assemble but do not start degraded arrays.\n"
e0d19036
NB
417;
418
419char Help_manage[] =
420"Usage: mdadm arraydevice options component devices...\n"
421"\n"
422"This usage is for managing the component devices within an array.\n"
423"The --manage option is not needed and is assumed if the first argument\n"
424"is a device name or a management option.\n"
425"The first device listed will be taken to be an md array device, and\n"
426"subsequent devices are (potential) components of that array.\n"
427"\n"
428"Options that are valid with management mode are:\n"
429" --add -a : hotadd subsequent devices to the array\n"
430" --remove -r : remove subsequent devices, which must not be active\n"
431" --fail -f : mark subsequent devices a faulty\n"
432" --set-faulty : same as --fail\n"
433" --run -R : start a partially built array\n"
5787fa49 434" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
435" --readonly -o : mark array as readonly\n"
436" --readwrite -w : mark array as readwrite\n"
437;
438
439char Help_misc[] =
440"Usage: mdadm misc_option devices...\n"
441"\n"
442"This usage is for performing some task on one or more devices, which\n"
443"may be arrays or components, depending on the task.\n"
444"The --misc option is not needed (though it is allowed) and is assumed\n"
445"if the first argument in a misc option.\n"
446"\n"
447"Options that are valid with the miscellaneous mode are:\n"
448" --query -Q : Display general information about how a\n"
449" device relates to the md driver\n"
450" --detail -D : Display details of an array\n"
5787fa49 451" --examine -E : Examine superblock on an array component\n"
c82f047c 452" --examine-bitmap -X: Display contents of a bitmap file\n"
e0d19036
NB
453" --zero-superblock : erase the MD superblock from a device.\n"
454" --run -R : start a partially built array\n"
5787fa49 455" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
456" --readonly -o : mark array as readonly\n"
457" --readwrite -w : mark array as readwrite\n"
feb716e9 458" --test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing\n"
e0d19036
NB
459;
460
461char Help_monitor[] =
462"Usage: mdadm --monitor options devices\n"
463"\n"
464"This usage causes mdadm to monitor a number of md arrays by periodically\n"
465"polling their status and acting on any changes.\n"
466"If any devices are listed then those devices are monitored, otherwise\n"
467"all devices listed in the config file are monitored.\n"
468"The address for mailing advisories to, and the program to handle\n"
469"each change can be specified in the config file or on the command line.\n"
470"If no mail address or program are specified, then mdadm reports all\n"
471"state changes to stdout.\n"
472"\n"
dd0781e5 473"Options that are valid with the monitor (-F --follow) mode are:\n"
e0d19036
NB
474" --mail= -m : Address to mail alerts of failure to\n"
475" --program= -p : Program to run when an event is detected\n"
476" --alert= : same as --program\n"
477" --delay= -d : seconds of delay between polling state. default=60\n"
478" --config= -c : specify a different config file\n"
479" --scan -s : find mail-address/program in config file\n"
d013a55e 480" --daemonise -f : Fork and continue in child, parent exits\n"
b5e64645 481" --pid-file= -i : In daemon mode write pid to specified file instead of stdout\n"
aa88f531 482" --oneshot -1 : Check for degraded arrays, then exit\n"
98c6faba 483" --test -t : Generate a TestMessage event against each array at startup\n"
e0d19036
NB
484;
485
dd0781e5
NB
486char Help_grow[] =
487"Usage: mdadm --grow device options\n"
488"\n"
489"This usage causes mdadm to attempt to reconfigure a running array.\n"
490"This is only possibly if the kernel being used supports a particular\n"
491"reconfiguration. This version only supports changing the number of\n"
492"devices in a RAID1, and changing the active size of all devices in\n"
493"a RAID1/4/5/6.\n"
494"\n"
891d2994 495"Options that are valid with the grow (-G --grow) mode are:\n"
dd0781e5
NB
496" --size= -z : Change the active size of devices in an array.\n"
497" : This is useful if all devices have been replaced\n"
498" : with larger devices.\n"
499" --raid-disks= -n : Change the number of active devices in a RAID1\n"
500" : array.\n"
501;
e0d19036
NB
502
503
504
505char Help_config[] =
506"The /etc/mdadm.conf config file:\n\n"
507" The config file contains, apart from blank lines and comment lines that\n"
508" start with a hash(#), four sorts of configuration lines: array lines, \n"
509" device lines, mailaddr lines and program lines.\n"
510" Each configuration line is constructed of a number of space separated\n"
511" words, and can be continued on subsequent physical lines by indenting\n"
512" those lines.\n"
513"\n"
514" A device line starts with the word 'device' and then has a number of words\n"
515" which identify devices. These words should be names of devices in the\n"
516" filesystem, and can contain wildcards. There can be multiple words or each\n"
517" device line, and multiple device lines. All devices so listed are checked\n"
518" for relevant super blocks when assembling arrays.\n"
519"\n"
520" An array line start with the word 'array'. This is followed by the name of\n"
521" the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
522" describe the identity of the array, used to recognise devices to include in the\n"
523" array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
524" as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
525" of devices. This is given as a comma separated list of names, possibly\n"
5787fa49 526" containing wildcards, preceded by 'devices='. If multiple critea are given,\n"
e0d19036
NB
527" than a device must match all of them to be considered.\n"
528"\n"
529" A mailaddr line starts with the word 'mailaddr' and should contain exactly\n"
530" one Email address. 'mdadm --monitor --scan' will send alerts of failed drives\n"
531" to this Email address."
532"\n"
533" A program line starts with the word 'program' and should contain exactly\n"
534" one program name. 'mdadm --monitor --scan' will run this program when any\n"
535" event is detected.\n"
64c4757e
NB
536"\n"
537;
682c7051
NB
538
539
540/* name/number mappings */
541
542mapping_t r5layout[] = {
cd29a5c8
NB
543 { "left-asymmetric", 0},
544 { "right-asymmetric", 1},
545 { "left-symmetric", 2},
546 { "right-symmetric", 3},
682c7051
NB
547
548 { "default", 2},
549 { "la", 0},
550 { "ra", 1},
551 { "ls", 2},
552 { "rs", 3},
553 { NULL, 0}
554};
555
556mapping_t pers[] = {
557 { "linear", -1},
558 { "raid0", 0},
559 { "0", 0},
560 { "stripe", 0},
561 { "raid1", 1},
562 { "1", 1},
563 { "mirror", 1},
564 { "raid4", 4},
565 { "4", 4},
566 { "raid5", 5},
567 { "5", 5},
e0d19036
NB
568 { "multipath", -4},
569 { "mp", -4},
98c6faba
NB
570 { "raid6", 6},
571 { "6", 6},
e5329c37
NB
572 { "raid10", 10},
573 { "10", 10},
b5e64645 574 { "faulty", -5},
682c7051
NB
575 { NULL, 0}
576};
e0d19036
NB
577
578
579mapping_t modes[] = {
580 { "assemble", ASSEMBLE},
581 { "build", BUILD},
582 { "create", CREATE},
583 { "manage", MANAGE},
584 { "misc", MISC},
585 { "monitor", MONITOR},
dd0781e5 586 { "grow", GROW},
e0d19036 587};
b5e64645
NB
588
589mapping_t faultylayout[] = {
590 { "write-transient", WriteTransient },
591 { "wt", WriteTransient },
592 { "read-transient", ReadTransient },
593 { "rt", ReadTransient },
594 { "write-persistent", WritePersistent },
595 { "wp", WritePersistent },
596 { "read-persistent", ReadPersistent },
597 { "rp", ReadPersistent },
598 { "write-all", WriteAll },
599 { "wa", WriteAll },
600 { "read-fixable", ReadFixable },
601 { "rf", ReadFixable },
602
603 { "clear", ClearErrors},
604 { "flush", ClearFaults},
605 { "none", ClearErrors},
606 { "default", ClearErrors},
607 { NULL, 0}
608};