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