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