]> git.ipfire.org Git - thirdparty/mdadm.git/blame - ReadMe.c
Make return code for "--detail --test" more reliable.
[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
e003092c 32char Version[] = Name " - v2.6.1 - 22nd February 2007\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
8382f19b
NB
94char short_options[]="-ABCDEFGIQhVXWvqbc:i:l:p:m:n:x:u:c:d:z:U:sarfRSow1tye:";
95char short_bitmap_auto_options[]=
96 "-ABCDEFGIQhVXWvqb:c:i:l:p:m:n:x:u:c:d:z:U:sa:rfRSow1tye:";
773135f5 97
64c4757e
NB
98struct option long_options[] = {
99 {"manage", 0, 0, '@'},
e0d19036 100 {"misc", 0, 0, '#'},
64c4757e
NB
101 {"assemble", 0, 0, 'A'},
102 {"build", 0, 0, 'B'},
103 {"create", 0, 0, 'C'},
104 {"detail", 0, 0, 'D'},
105 {"examine", 0, 0, 'E'},
52826846 106 {"follow", 0, 0, 'F'},
dd0781e5 107 {"grow", 0, 0, 'G'},
8382f19b 108 {"incremental",0,0, 'I'},
e0d19036
NB
109 {"zero-superblock", 0, 0, 'K'}, /* deliberately no a short_option */
110 {"query", 0, 0, 'Q'},
c82f047c 111 {"examine-bitmap", 0, 0, 'X'},
1f48664b 112 {"auto-detect", 0, 0, AutoDetect},
52826846
NB
113
114 /* synonyms */
115 {"monitor", 0, 0, 'F'},
116
64c4757e
NB
117 /* after those will normally come the name of the md device */
118 {"help", 0, 0, 'h'},
56eedc1a 119 {"help-options",0,0,'h'},
64c4757e
NB
120 {"version", 0, 0, 'V'},
121 {"verbose", 0, 0, 'v'},
dab6685f 122 {"quiet", 0, 0, 'q'},
64c4757e
NB
123
124 /* For create or build: */
125 {"chunk", 1, 0, 'c'},
126 {"rounding", 1, 0, 'c'}, /* for linear, chunk is really a rounding number */
98c6faba 127 {"level", 1, 0, 'l'}, /* 0,1,4,5,6,linear */
5787fa49 128 {"parity", 1, 0, 'p'}, /* {left,right}-{a,}symmetric */
64c4757e
NB
129 {"layout", 1, 0, 'p'},
130 {"raid-disks",1, 0, 'n'},
b83d95f3 131 {"raid-devices",1, 0, 'n'},
64c4757e 132 {"spare-disks",1,0, 'x'},
b83d95f3 133 {"spare-devices",1,0, 'x'},
dd0781e5 134 {"size", 1, 0, 'z'},
c82f047c 135 {"auto", 1, 0, 'a'}, /* also for --assemble */
997aed5d 136 {"assume-clean",0,0, AssumeClean },
f9ce90ba 137 {"metadata", 1, 0, 'e'}, /* superblock format */
c82f047c 138 {"bitmap", 1, 0, 'b'},
997aed5d
NB
139 {"bitmap-chunk", 1, 0, BitmapChunk},
140 {"write-behind", 2, 0, WriteBehind},
dfd4d8ee 141 {"write-mostly",0, 0, 'W'},
997aed5d
NB
142 {"re-add", 0, 0, ReAdd},
143 {"homehost", 1, 0, HomeHost},
589395d6 144 {"auto-update-homehost", 0, 0, AutoHomeHost},
38098016 145 {"symlinks", 1, 0, Symlinks},
64c4757e
NB
146
147 /* For assemble */
148 {"uuid", 1, 0, 'u'},
52826846 149 {"super-minor",1,0, 'm'},
947fd4dd 150 {"name", 1, 0, 'N'},
64c4757e
NB
151 {"config", 1, 0, 'c'},
152 {"scan", 0, 0, 's'},
153 {"force", 0, 0, 'f'},
5787fa49 154 {"update", 1, 0, 'U'},
dfd4d8ee 155
64c4757e
NB
156 /* Management */
157 {"add", 0, 0, 'a'},
158 {"remove", 0, 0, 'r'},
159 {"fail", 0, 0, 'f'},
160 {"set-faulty",0, 0, 'f'},
161 {"run", 0, 0, 'R'},
162 {"stop", 0, 0, 'S'},
163 {"readonly", 0, 0, 'o'},
164 {"readwrite", 0, 0, 'w'},
997aed5d 165 {"no-degraded",0,0, NoDegraded },
b90c0e9a 166 {"wait", 0, 0, 'W'},
52826846 167
cd29a5c8
NB
168 /* For Detail/Examine */
169 {"brief", 0, 0, 'b'},
54bad364 170 {"export", 0, 0, 'Y'},
997aed5d 171 {"sparc2.2", 0, 0, Sparc22},
feb716e9 172 {"test", 0, 0, 't'},
cd29a5c8 173
52826846
NB
174 /* For Follow/monitor */
175 {"mail", 1, 0, 'm'},
176 {"program", 1, 0, 'p'},
177 {"alert", 1, 0, 'p'},
178 {"delay", 1, 0, 'd'},
56eedc1a
NB
179 {"daemonise", 0, 0, 'f'},
180 {"daemonize", 0, 0, 'f'},
aa88f531 181 {"oneshot", 0, 0, '1'},
b5e64645 182 {"pid-file", 1, 0, 'i'},
90cf1ddd 183 {"syslog", 0, 0, 'y'},
06b0d786 184 /* For Grow */
997aed5d 185 {"backup-file", 1,0, BackupFile},
8382f19b
NB
186
187 /* For Incremental */
188 {"rebuild-map", 0, 0, 'r'},
64c4757e
NB
189 {0, 0, 0, 0}
190};
191
192char Usage[] =
9a9dab36 193"Usage: mdadm --help\n"
64c4757e
NB
194" for help\n"
195;
196
197char Help[] =
e5a5d81e
NB
198"mdadm is used for building, managing, and monitoring\n"
199"Linux md devices (aka RAID arrays)\n"
9a9dab36 200"Usage: mdadm --create device options...\n"
e5a5d81e 201" Create a new array from unused devices.\n"
9a9dab36 202" mdadm --assemble device options...\n"
e968ba60 203" Assemble a previously created array.\n"
9a9dab36 204" mdadm --build device options...\n"
e5a5d81e 205" Create or assemble an array without metadata.\n"
e0d19036 206" mdadm --manage device options...\n"
e968ba60 207" make changes to an existing array.\n"
e0d19036 208" mdadm --misc options... devices\n"
e968ba60 209" report on or modify various md related devices.\n"
8382f19b
NB
210" mdadm --grow options device\n"
211" resize/reshape an active array\n"
212" mdadm --incremental device\n"
213" add a device to an array as appropriate\n"
e0d19036 214" mdadm --monitor options...\n"
e968ba60 215" Monitor one or more array for significant changes.\n"
9a9dab36 216" mdadm device options...\n"
e968ba60 217" Shorthand for --manage.\n"
e5a5d81e
NB
218"Any parameter that does not start with '-' is treated as a device name\n"
219"or, for --examine-bitmap, a file name.\n"
220"The first such name is often the name of an md device. Subsequent\n"
221"names are often names of component devices.\n"
222"\n"
56eedc1a 223" For detailed help on the above major modes use --help after the mode\n"
e0d19036 224" e.g.\n"
9a9dab36 225" mdadm --assemble --help\n"
56eedc1a
NB
226" For general help on options use\n"
227" mdadm --help-options\n"
228;
229
230char OptionHelp[] =
64c4757e 231"Any parameter that does not start with '-' is treated as a device name\n"
c82f047c 232"or, for --examine-bitmap, a file name.\n"
e0d19036 233"The first such name is often the name of an md device. Subsequent\n"
e5a5d81e 234"names are often names of component devices.\n"
52826846 235"\n"
e0d19036 236"Some common options are:\n"
56eedc1a 237" --help -h : General help message or, after above option,\n"
64c4757e 238" mode specific help message\n"
56eedc1a 239" --help-options : This help message\n"
9a9dab36 240" --version -V : Print version information for mdadm\n"
64c4757e 241" --verbose -v : Be more verbose about what is happening\n"
dab6685f 242" --quiet -q : Don't print un-necessary messages\n"
e0d19036 243" --brief -b : Be less verbose, more brief\n"
54bad364
KS
244" --export -Y : With --detail, use key=value format for easy\n"
245" import into environment\n"
e0d19036
NB
246" --force -f : Override normal checks and be more forceful\n"
247"\n"
248" --assemble -A : Assemble an array\n"
e5a5d81e 249" --build -B : Build an array without metadata\n"
e0d19036
NB
250" --create -C : Create a new array\n"
251" --detail -D : Display details of an array\n"
5787fa49 252" --examine -E : Examine superblock on an array component\n"
c82f047c 253" --examine-bitmap -X: Display the detail of a bitmap file\n"
e0d19036 254" --monitor -F : monitor (follow) some arrays\n"
8382f19b
NB
255" --grow -G : resize/ reshape and array\n"
256" --incremental -I : add a single device to an array as appropriate\n"
e0d19036
NB
257" --query -Q : Display general information about how a\n"
258" device relates to the md driver\n"
1f48664b 259" --auto-detect : Start arrays auto-detected by the kernel\n"
e0d19036
NB
260;
261/*
64c4757e
NB
262"\n"
263" For create or build:\n"
c82f047c 264" --bitmap= -b : File to store bitmap in - may pre-exist for --build\n"
64c4757e 265" --chunk= -c : chunk size of kibibytes\n"
5787fa49 266" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
267" --level= -l : raid level: 0,1,4,5,6,linear,mp. 0 or linear for build\n"
268" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
64c4757e 269" --layout= : same as --parity\n"
b83d95f3
NB
270" --raid-devices= -n : number of active devices in array\n"
271" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
e5329c37 272" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
52826846
NB
273" --force -f : Honour devices as listed on command line. Don't\n"
274" : insert a missing drive for RAID5.\n"
dd0781e5
NB
275" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
276" --assume-clean : Assume the array is already in-sync. This is dangerous.\n"
c82f047c
NB
277" --bitmap-chunk= : chunksize of bitmap in bitmap file (Kilobytes)\n"
278" --delay= -d : seconds between bitmap updates\n"
dfd4d8ee 279" --write-behind= : number of simultaneous write-behind requests to allow (requires bitmap)\n"
947fd4dd 280" --name= -N : Textual name for array - max 32 characters\n"
64c4757e
NB
281"\n"
282" For assemble:\n"
c82f047c 283" --bitmap= -b : File to find bitmap information in\n"
64c4757e
NB
284" --uuid= -u : uuid of array to assemble. Devices which don't\n"
285" have this uuid are excluded\n"
52826846
NB
286" --super-minor= -m : minor number to look for in super-block when\n"
287" choosing devices to use.\n"
947fd4dd 288" --name= -N : Array name to look for in super-block.\n"
64c4757e
NB
289" --config= -c : config file\n"
290" --scan -s : scan config file for missing information\n"
291" --force -f : Assemble the array even if some superblocks appear out-of-date\n"
cbfbcb0b 292" --update= -U : Update superblock: try '-A --update=?' for list of options.\n"
dd0781e5 293" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
b8a8ccf9 294" --no-degraded : Do not start any degraded arrays - default unless --scan.\n"
64c4757e 295"\n"
cd29a5c8
NB
296" For detail or examine:\n"
297" --brief -b : Just print device name and UUID\n"
298"\n"
52826846
NB
299" For follow/monitor:\n"
300" --mail= -m : Address to mail alerts of failure to\n"
301" --program= -p : Program to run when an event is detected\n"
302" --alert= : same as --program\n"
303" --delay= -d : seconds of delay between polling state. default=60\n"
304"\n"
64c4757e
NB
305" General management:\n"
306" --add -a : add, or hotadd subsequent devices\n"
307" --remove -r : remove subsequent devices\n"
308" --fail -f : mark subsequent devices a faulty\n"
309" --set-faulty : same as --fail\n"
310" --run -R : start a partially built array\n"
5787fa49 311" --stop -S : deactivate array, releasing all resources\n"
64c4757e
NB
312" --readonly -o : mark array as readonly\n"
313" --readwrite -w : mark array as readwrite\n"
9a9dab36 314" --zero-superblock : erase the MD superblock from a device.\n"
b90c0e9a 315" --wait -W : wait for recovery/resync/reshape to finish.\n"
64c4757e 316;
e0d19036 317*/
64c4757e
NB
318
319char Help_create[] =
b83d95f3 320"Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e 321"\n"
aa88f531
NB
322" This usage will initialise a new md array, associate some\n"
323" devices with it, and activate the array. In order to create an\n"
324" array with some devices missing, use the special word 'missing' in\n"
325" place of the relevant device name.\n"
64c4757e 326"\n"
aa88f531 327" Before devices are added, they are checked to see if they already contain\n"
e0d19036 328" raid superblocks or filesystems. They are also checked to see if\n"
64c4757e 329" the variance in device size exceeds 1%.\n"
aa88f531
NB
330" If any discrepancy is found, the user will be prompted for confirmation\n"
331" before the array is created. The presence of a '--run' can override this\n"
64c4757e
NB
332" caution.\n"
333"\n"
e0d19036
NB
334" If the --size option is given then only that many kilobytes of each\n"
335" device is used, no matter how big each device is.\n"
682c7051 336" If no --size is given, the apparent size of the smallest drive given\n"
e0d19036
NB
337" is used for raid level 1 and greater, and the full device is used for\n"
338" other levels.\n"
682c7051 339"\n"
e0d19036 340" Options that are valid with --create (-C) are:\n"
c82f047c 341" --bitmap= : Create a bitmap for the array with the given filename\n"
e0d19036 342" --chunk= -c : chunk size of kibibytes\n"
5787fa49 343" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
344" --level= -l : raid level: 0,1,4,5,6,linear,multipath and synonyms\n"
345" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
e0d19036 346" --layout= : same as --parity\n"
b83d95f3
NB
347" --raid-devices= -n : number of active devices in array\n"
348" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
e5329c37 349" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
e0d19036
NB
350" --force -f : Honour devices as listed on command line. Don't\n"
351" : insert a missing drive for RAID5.\n"
aa88f531 352" --run -R : insist of running the array even if not all\n"
e0d19036 353" : devices are present or some look odd.\n"
aa88f531 354" --readonly -o : start the array readonly - not supported yet.\n"
947fd4dd 355" --name= -N : Textual name for array - max 32 characters\n"
c82f047c
NB
356" --bitmap-chunk= : bitmap chunksize in Kilobytes.\n"
357" --delay= -d : bitmap update delay in seconds.\n"
64c4757e
NB
358"\n"
359;
360
361char Help_build[] =
b83d95f3 362"Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e
NB
363"\n"
364" This usage is similar to --create. The difference is that it creates\n"
e0d19036 365" a legacy array without a superblock. With these arrays there is no\n"
64c4757e
NB
366" different between initially creating the array and subsequently\n"
367" assembling the array, except that hopefully there is useful data\n"
368" there in the second case.\n"
369"\n"
e0d19036 370" The level may only be 0, raid0, or linear.\n"
64c4757e 371" All devices must be listed and the array will be started once complete.\n"
e0d19036 372" Options that are valid with --build (-B) are:\n"
c82f047c 373" --bitmap= : file to store/find bitmap information in.\n"
e0d19036 374" --chunk= -c : chunk size of kibibytes\n"
5787fa49 375" --rounding= : rounding factor for linear array (==chunk size)\n"
e0d19036 376" --level= -l : 0, raid0, or linear\n"
c82f047c
NB
377" --raid-devices= -n : number of active devices in array\n"
378" --bitmap-chunk= : bitmap chunksize in Kilobytes.\n"
379" --delay= -d : bitmap update delay in seconds.\n"
64c4757e
NB
380;
381
382char Help_assemble[] =
9a9dab36
NB
383"Usage: mdadm --assemble device options...\n"
384" mdadm --assemble --scan options...\n"
64c4757e
NB
385"\n"
386"This usage assembles one or more raid arrays from pre-existing\n"
387"components.\n"
e0d19036 388"For each array, mdadm needs to know the md device, the identity of\n"
52826846
NB
389"the array, and a number of sub devices. These can be found in a number\n"
390"of ways.\n"
391"\n"
392"The md device is either given on the command line or is found listed\n"
393"in the config file. The array identity is determined either from the\n"
e0d19036 394"--uuid or --super-minor commandline arguments, from the config file,\n"
52826846 395"or from the first component device on the command line.\n"
64c4757e 396"\n"
52826846
NB
397"The different combinations of these are as follows:\n"
398" If the --scan option is not given, then only devices and identities\n"
399" listed on the command line are considered.\n"
e0d19036 400" The first device will be the array device, and the remainder will be\n"
52826846
NB
401" examined when looking for components.\n"
402" If an explicit identity is given with --uuid or --super-minor, then\n"
e0d19036 403" only devices with a superblock which matches that identity is considered,\n"
52826846 404" otherwise every device listed is considered.\n"
64c4757e 405"\n"
52826846
NB
406" If the --scan option is given, and no devices are listed, then\n"
407" every array listed in the config file is considered for assembly.\n"
e0d19036 408" The identity of candidate devices are determined from the config file.\n"
64c4757e 409"\n"
52826846
NB
410" If the --scan option is given as well as one or more devices, then\n"
411" Those devices are md devices that are to be assembled. Their identity\n"
412" and components are determined from the config file.\n"
64c4757e 413"\n"
b8a8ccf9
NB
414" If mdadm can not find all of the components for an array, it will assemble\n"
415" it but not activate it unless --run or --scan is given. To preserve this\n"
416" behaviour even with --scan, add --no-degraded. Note that \"all of the\n"
417" components\" means as many as were present the last time the array was running\n"
418" as recorded in the superblock. If the array was already degraded, and\n"
419" the missing device is not a new problem, it will still be assembled. It\n"
420" is only newly missing devices that cause the array not to be started.\n"
421"\n"
e0d19036 422"Options that are valid with --assemble (-A) are:\n"
c82f047c 423" --bitmap= : bitmap file to use wit the array\n"
e0d19036
NB
424" --uuid= -u : uuid of array to assemble. Devices which don't\n"
425" have this uuid are excluded\n"
426" --super-minor= -m : minor number to look for in super-block when\n"
427" choosing devices to use.\n"
947fd4dd 428" --name= -N : Array name to look for in super-block.\n"
e0d19036
NB
429" --config= -c : config file\n"
430" --scan -s : scan config file for missing information\n"
431" --run -R : Try to start the array even if not enough devices\n"
432" for a full array are present\n"
433" --force -f : Assemble the array even if some superblocks appear\n"
434" : out-of-date. This involves modifying the superblocks.\n"
cbfbcb0b 435" --update= -U : Update superblock: try '-A --update=?' for option list.\n"
b8a8ccf9 436" --no-degraded : Assemble but do not start degraded arrays.\n"
e0d19036
NB
437;
438
439char Help_manage[] =
440"Usage: mdadm arraydevice options component devices...\n"
441"\n"
442"This usage is for managing the component devices within an array.\n"
443"The --manage option is not needed and is assumed if the first argument\n"
444"is a device name or a management option.\n"
445"The first device listed will be taken to be an md array device, and\n"
446"subsequent devices are (potential) components of that array.\n"
447"\n"
448"Options that are valid with management mode are:\n"
449" --add -a : hotadd subsequent devices to the array\n"
450" --remove -r : remove subsequent devices, which must not be active\n"
451" --fail -f : mark subsequent devices a faulty\n"
452" --set-faulty : same as --fail\n"
453" --run -R : start a partially built array\n"
5787fa49 454" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
455" --readonly -o : mark array as readonly\n"
456" --readwrite -w : mark array as readwrite\n"
457;
458
459char Help_misc[] =
460"Usage: mdadm misc_option devices...\n"
461"\n"
462"This usage is for performing some task on one or more devices, which\n"
463"may be arrays or components, depending on the task.\n"
464"The --misc option is not needed (though it is allowed) and is assumed\n"
465"if the first argument in a misc option.\n"
466"\n"
467"Options that are valid with the miscellaneous mode are:\n"
468" --query -Q : Display general information about how a\n"
469" device relates to the md driver\n"
470" --detail -D : Display details of an array\n"
5787fa49 471" --examine -E : Examine superblock on an array component\n"
c82f047c 472" --examine-bitmap -X: Display contents of a bitmap file\n"
e0d19036
NB
473" --zero-superblock : erase the MD superblock from a device.\n"
474" --run -R : start a partially built array\n"
5787fa49 475" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
476" --readonly -o : mark array as readonly\n"
477" --readwrite -w : mark array as readwrite\n"
feb716e9 478" --test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing\n"
b90c0e9a 479" --wait -W : wait for resync/rebuild/recovery to finish\n"
e0d19036
NB
480;
481
482char Help_monitor[] =
483"Usage: mdadm --monitor options devices\n"
484"\n"
485"This usage causes mdadm to monitor a number of md arrays by periodically\n"
486"polling their status and acting on any changes.\n"
487"If any devices are listed then those devices are monitored, otherwise\n"
488"all devices listed in the config file are monitored.\n"
489"The address for mailing advisories to, and the program to handle\n"
490"each change can be specified in the config file or on the command line.\n"
491"If no mail address or program are specified, then mdadm reports all\n"
492"state changes to stdout.\n"
493"\n"
dd0781e5 494"Options that are valid with the monitor (-F --follow) mode are:\n"
e0d19036
NB
495" --mail= -m : Address to mail alerts of failure to\n"
496" --program= -p : Program to run when an event is detected\n"
497" --alert= : same as --program\n"
498" --delay= -d : seconds of delay between polling state. default=60\n"
499" --config= -c : specify a different config file\n"
500" --scan -s : find mail-address/program in config file\n"
d013a55e 501" --daemonise -f : Fork and continue in child, parent exits\n"
b5e64645 502" --pid-file= -i : In daemon mode write pid to specified file instead of stdout\n"
aa88f531 503" --oneshot -1 : Check for degraded arrays, then exit\n"
98c6faba 504" --test -t : Generate a TestMessage event against each array at startup\n"
e0d19036
NB
505;
506
dd0781e5
NB
507char Help_grow[] =
508"Usage: mdadm --grow device options\n"
509"\n"
510"This usage causes mdadm to attempt to reconfigure a running array.\n"
511"This is only possibly if the kernel being used supports a particular\n"
00be0b12
NB
512"reconfiguration. This version supports changing the number of\n"
513"devices in a RAID1/5/6, changing the active size of all devices in\n"
514"a RAID1/4/5/6, adding or removing a write-intent bitmap, and changing\n"
515"the error mode for a 'FAULTY' array.\n"
dd0781e5 516"\n"
891d2994 517"Options that are valid with the grow (-G --grow) mode are:\n"
00be0b12
NB
518" --level= -l : Tell mdadm what level the array is so that it can\n"
519" : interpret '--layout' properly.\n"
520" --layout= -p : For a FAULTY array, set/change the error mode.\n"
dd0781e5
NB
521" --size= -z : Change the active size of devices in an array.\n"
522" : This is useful if all devices have been replaced\n"
523" : with larger devices.\n"
00be0b12 524" --raid-disks= -n : Change the number of active devices in an array.\n"
dd0781e5 525" : array.\n"
00be0b12 526" --bitmap= -b : Add or remove a write-intent bitmap.\n"
dd0781e5 527;
e0d19036 528
8382f19b
NB
529char Help_incr[] =
530"Usage: mdadm --incremental [-Rqrs] device\n"
531"\n"
532"This usage allows for incremental assembly of md arrays. Devices can be\n"
533"added one at a time as they are discovered. Once an array has all expected\n"
534"devices, it will be started.\n"
535"\n"
536"Options that are valid with incremental assembly (-I --incremental) more are:\n"
537" --run -R : run arrays as soon as a minimal number of devices are\n"
538" : present rather than waiting for all expected.\n"
539" --quiet -q : Don't print any information messages, just errors.\n"
540" --rebuild -r : Rebuild the 'map' file that mdadm uses for tracking\n"
541" : partial arrays.\n"
542" --scan -s : Use with -R to start any arrays that have the minimal\n"
543" : required number of devices, but are not yet started.\n"
544;
e0d19036
NB
545
546char Help_config[] =
547"The /etc/mdadm.conf config file:\n\n"
548" The config file contains, apart from blank lines and comment lines that\n"
549" start with a hash(#), four sorts of configuration lines: array lines, \n"
550" device lines, mailaddr lines and program lines.\n"
551" Each configuration line is constructed of a number of space separated\n"
552" words, and can be continued on subsequent physical lines by indenting\n"
553" those lines.\n"
554"\n"
555" A device line starts with the word 'device' and then has a number of words\n"
556" which identify devices. These words should be names of devices in the\n"
557" filesystem, and can contain wildcards. There can be multiple words or each\n"
558" device line, and multiple device lines. All devices so listed are checked\n"
559" for relevant super blocks when assembling arrays.\n"
560"\n"
561" An array line start with the word 'array'. This is followed by the name of\n"
562" the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
563" describe the identity of the array, used to recognise devices to include in the\n"
564" array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
565" as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
566" of devices. This is given as a comma separated list of names, possibly\n"
5787fa49 567" containing wildcards, preceded by 'devices='. If multiple critea are given,\n"
e0d19036
NB
568" than a device must match all of them to be considered.\n"
569"\n"
570" A mailaddr line starts with the word 'mailaddr' and should contain exactly\n"
571" one Email address. 'mdadm --monitor --scan' will send alerts of failed drives\n"
572" to this Email address."
573"\n"
574" A program line starts with the word 'program' and should contain exactly\n"
575" one program name. 'mdadm --monitor --scan' will run this program when any\n"
576" event is detected.\n"
64c4757e
NB
577"\n"
578;
682c7051
NB
579
580
581/* name/number mappings */
582
583mapping_t r5layout[] = {
cd29a5c8
NB
584 { "left-asymmetric", 0},
585 { "right-asymmetric", 1},
586 { "left-symmetric", 2},
587 { "right-symmetric", 3},
682c7051
NB
588
589 { "default", 2},
590 { "la", 0},
591 { "ra", 1},
592 { "ls", 2},
593 { "rs", 3},
594 { NULL, 0}
595};
596
597mapping_t pers[] = {
598 { "linear", -1},
599 { "raid0", 0},
600 { "0", 0},
601 { "stripe", 0},
602 { "raid1", 1},
603 { "1", 1},
604 { "mirror", 1},
605 { "raid4", 4},
606 { "4", 4},
607 { "raid5", 5},
608 { "5", 5},
e0d19036
NB
609 { "multipath", -4},
610 { "mp", -4},
98c6faba
NB
611 { "raid6", 6},
612 { "6", 6},
e5329c37
NB
613 { "raid10", 10},
614 { "10", 10},
b5e64645 615 { "faulty", -5},
682c7051
NB
616 { NULL, 0}
617};
e0d19036
NB
618
619
620mapping_t modes[] = {
621 { "assemble", ASSEMBLE},
622 { "build", BUILD},
623 { "create", CREATE},
624 { "manage", MANAGE},
625 { "misc", MISC},
626 { "monitor", MONITOR},
dd0781e5 627 { "grow", GROW},
8382f19b 628 { "incremental", INCREMENTAL},
1f48664b 629 { "auto-detect", AUTODETECT},
e0d19036 630};
b5e64645
NB
631
632mapping_t faultylayout[] = {
633 { "write-transient", WriteTransient },
634 { "wt", WriteTransient },
635 { "read-transient", ReadTransient },
636 { "rt", ReadTransient },
637 { "write-persistent", WritePersistent },
638 { "wp", WritePersistent },
639 { "read-persistent", ReadPersistent },
640 { "rp", ReadPersistent },
641 { "write-all", WriteAll },
642 { "wa", WriteAll },
643 { "read-fixable", ReadFixable },
644 { "rf", ReadFixable },
645
646 { "clear", ClearErrors},
647 { "flush", ClearFaults},
648 { "none", ClearErrors},
649 { "default", ClearErrors},
650 { NULL, 0}
651};