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