]> git.ipfire.org Git - thirdparty/mdadm.git/blame - ReadMe.c
Separate sueprblock handling into separate file
[thirdparty/mdadm.git] / ReadMe.c
CommitLineData
64c4757e 1/*
9a9dab36 2 * mdadm - manage Linux "md" devices aka RAID arrays.
64c4757e 3 *
cd29a5c8 4 * Copyright (C) 2001-2002 Neil Brown <neilb@cse.unsw.edu.au>
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
e5811618 32char Version[] = Name " - v1.11.0 - 11 April 2005\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
b5e64645 94char short_options[]="-ABCDEFGQhVvbc:i:l:p:m:n:x:u:c:d:z:U:sa::rfRSow1t";
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'},
e0d19036
NB
105 {"zero-superblock", 0, 0, 'K'}, /* deliberately no a short_option */
106 {"query", 0, 0, 'Q'},
52826846
NB
107
108 /* synonyms */
109 {"monitor", 0, 0, 'F'},
110
64c4757e
NB
111 /* after those will normally come the name of the md device */
112 {"help", 0, 0, 'h'},
56eedc1a 113 {"help-options",0,0,'h'},
64c4757e
NB
114 {"version", 0, 0, 'V'},
115 {"verbose", 0, 0, 'v'},
116
117 /* For create or build: */
118 {"chunk", 1, 0, 'c'},
119 {"rounding", 1, 0, 'c'}, /* for linear, chunk is really a rounding number */
98c6faba 120 {"level", 1, 0, 'l'}, /* 0,1,4,5,6,linear */
5787fa49 121 {"parity", 1, 0, 'p'}, /* {left,right}-{a,}symmetric */
64c4757e
NB
122 {"layout", 1, 0, 'p'},
123 {"raid-disks",1, 0, 'n'},
b83d95f3 124 {"raid-devices",1, 0, 'n'},
64c4757e 125 {"spare-disks",1,0, 'x'},
b83d95f3 126 {"spare-devices",1,0, 'x'},
dd0781e5
NB
127 {"size", 1, 0, 'z'},
128 {"auto", 2, 0, 'a'}, /* also for --assemble */
129 {"assume-clean",0,0, 3 },
64c4757e
NB
130
131 /* For assemble */
132 {"uuid", 1, 0, 'u'},
52826846 133 {"super-minor",1,0, 'm'},
64c4757e
NB
134 {"config", 1, 0, 'c'},
135 {"scan", 0, 0, 's'},
136 {"force", 0, 0, 'f'},
5787fa49 137 {"update", 1, 0, 'U'},
64c4757e
NB
138 /* Management */
139 {"add", 0, 0, 'a'},
140 {"remove", 0, 0, 'r'},
141 {"fail", 0, 0, 'f'},
142 {"set-faulty",0, 0, 'f'},
143 {"run", 0, 0, 'R'},
144 {"stop", 0, 0, 'S'},
145 {"readonly", 0, 0, 'o'},
146 {"readwrite", 0, 0, 'w'},
52826846 147
cd29a5c8
NB
148 /* For Detail/Examine */
149 {"brief", 0, 0, 'b'},
bd526cee 150 {"sparc2.2", 0, 0, 22},
feb716e9 151 {"test", 0, 0, 't'},
cd29a5c8 152
52826846
NB
153 /* For Follow/monitor */
154 {"mail", 1, 0, 'm'},
155 {"program", 1, 0, 'p'},
156 {"alert", 1, 0, 'p'},
157 {"delay", 1, 0, 'd'},
56eedc1a
NB
158 {"daemonise", 0, 0, 'f'},
159 {"daemonize", 0, 0, 'f'},
aa88f531 160 {"oneshot", 0, 0, '1'},
b5e64645 161 {"pid-file", 1, 0, 'i'},
64c4757e
NB
162
163 {0, 0, 0, 0}
164};
165
166char Usage[] =
9a9dab36 167"Usage: mdadm --help\n"
64c4757e
NB
168" for help\n"
169;
170
171char Help[] =
9a9dab36
NB
172"Usage: mdadm --create device options...\n"
173" mdadm --assemble device options...\n"
174" mdadm --build device options...\n"
e0d19036
NB
175" mdadm --manage device options...\n"
176" mdadm --misc options... devices\n"
177" mdadm --monitor options...\n"
9a9dab36 178" mdadm device options...\n"
5787fa49 179" mdadm is used for building, managing, and monitoring\n"
56eedc1a
NB
180" Linux md devices (aka RAID arrays)\n"
181" For detailed help on the above major modes use --help after the mode\n"
e0d19036 182" e.g.\n"
9a9dab36 183" mdadm --assemble --help\n"
56eedc1a
NB
184" For general help on options use\n"
185" mdadm --help-options\n"
186;
187
188char OptionHelp[] =
64c4757e 189"Any parameter that does not start with '-' is treated as a device name\n"
e0d19036
NB
190"The first such name is often the name of an md device. Subsequent\n"
191"names are often names of component devices."
52826846 192"\n"
e0d19036 193"Some common options are:\n"
56eedc1a 194" --help -h : General help message or, after above option,\n"
64c4757e 195" mode specific help message\n"
56eedc1a 196" --help-options : This help message\n"
9a9dab36 197" --version -V : Print version information for mdadm\n"
64c4757e 198" --verbose -v : Be more verbose about what is happening\n"
e0d19036
NB
199" --brief -b : Be less verbose, more brief\n"
200" --force -f : Override normal checks and be more forceful\n"
201"\n"
202" --assemble -A : Assemble an array\n"
203" --build -B : Build a legacy array\n"
204" --create -C : Create a new array\n"
205" --detail -D : Display details of an array\n"
5787fa49 206" --examine -E : Examine superblock on an array component\n"
e0d19036
NB
207" --monitor -F : monitor (follow) some arrays\n"
208" --query -Q : Display general information about how a\n"
209" device relates to the md driver\n"
210;
211/*
64c4757e
NB
212"\n"
213" For create or build:\n"
214" --chunk= -c : chunk size of kibibytes\n"
5787fa49 215" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
216" --level= -l : raid level: 0,1,4,5,6,linear,mp. 0 or linear for build\n"
217" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
64c4757e 218" --layout= : same as --parity\n"
b83d95f3
NB
219" --raid-devices= -n : number of active devices in array\n"
220" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
e5329c37 221" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
52826846
NB
222" --force -f : Honour devices as listed on command line. Don't\n"
223" : insert a missing drive for RAID5.\n"
dd0781e5
NB
224" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
225" --assume-clean : Assume the array is already in-sync. This is dangerous.\n"
64c4757e
NB
226"\n"
227" For assemble:\n"
228" --uuid= -u : uuid of array to assemble. Devices which don't\n"
229" have this uuid are excluded\n"
52826846
NB
230" --super-minor= -m : minor number to look for in super-block when\n"
231" choosing devices to use.\n"
64c4757e
NB
232" --config= -c : config file\n"
233" --scan -s : scan config file for missing information\n"
234" --force -f : Assemble the array even if some superblocks appear out-of-date\n"
feb716e9 235" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
dd0781e5 236" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
64c4757e 237"\n"
cd29a5c8
NB
238" For detail or examine:\n"
239" --brief -b : Just print device name and UUID\n"
240"\n"
52826846
NB
241" For follow/monitor:\n"
242" --mail= -m : Address to mail alerts of failure to\n"
243" --program= -p : Program to run when an event is detected\n"
244" --alert= : same as --program\n"
245" --delay= -d : seconds of delay between polling state. default=60\n"
246"\n"
64c4757e
NB
247" General management:\n"
248" --add -a : add, or hotadd subsequent devices\n"
249" --remove -r : remove subsequent devices\n"
250" --fail -f : mark subsequent devices a faulty\n"
251" --set-faulty : same as --fail\n"
252" --run -R : start a partially built array\n"
5787fa49 253" --stop -S : deactivate array, releasing all resources\n"
64c4757e
NB
254" --readonly -o : mark array as readonly\n"
255" --readwrite -w : mark array as readwrite\n"
9a9dab36 256" --zero-superblock : erase the MD superblock from a device.\n"
64c4757e 257;
e0d19036 258*/
64c4757e
NB
259
260char Help_create[] =
b83d95f3 261"Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e 262"\n"
aa88f531
NB
263" This usage will initialise a new md array, associate some\n"
264" devices with it, and activate the array. In order to create an\n"
265" array with some devices missing, use the special word 'missing' in\n"
266" place of the relevant device name.\n"
64c4757e 267"\n"
aa88f531 268" Before devices are added, they are checked to see if they already contain\n"
e0d19036 269" raid superblocks or filesystems. They are also checked to see if\n"
64c4757e 270" the variance in device size exceeds 1%.\n"
aa88f531
NB
271" If any discrepancy is found, the user will be prompted for confirmation\n"
272" before the array is created. The presence of a '--run' can override this\n"
64c4757e
NB
273" caution.\n"
274"\n"
e0d19036
NB
275" If the --size option is given then only that many kilobytes of each\n"
276" device is used, no matter how big each device is.\n"
682c7051 277" If no --size is given, the apparent size of the smallest drive given\n"
e0d19036
NB
278" is used for raid level 1 and greater, and the full device is used for\n"
279" other levels.\n"
682c7051 280"\n"
e0d19036
NB
281" Options that are valid with --create (-C) are:\n"
282" --chunk= -c : chunk size of kibibytes\n"
5787fa49 283" --rounding= : rounding factor for linear array (==chunk size)\n"
98c6faba
NB
284" --level= -l : raid level: 0,1,4,5,6,linear,multipath and synonyms\n"
285" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
e0d19036 286" --layout= : same as --parity\n"
b83d95f3
NB
287" --raid-devices= -n : number of active devices in array\n"
288" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
e5329c37 289" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
e0d19036
NB
290" --force -f : Honour devices as listed on command line. Don't\n"
291" : insert a missing drive for RAID5.\n"
aa88f531 292" --run -R : insist of running the array even if not all\n"
e0d19036 293" : devices are present or some look odd.\n"
aa88f531 294" --readonly -o : start the array readonly - not supported yet.\n"
64c4757e
NB
295"\n"
296;
297
298char Help_build[] =
b83d95f3 299"Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e
NB
300"\n"
301" This usage is similar to --create. The difference is that it creates\n"
e0d19036 302" a legacy array without a superblock. With these arrays there is no\n"
64c4757e
NB
303" different between initially creating the array and subsequently\n"
304" assembling the array, except that hopefully there is useful data\n"
305" there in the second case.\n"
306"\n"
e0d19036 307" The level may only be 0, raid0, or linear.\n"
64c4757e 308" All devices must be listed and the array will be started once complete.\n"
e0d19036
NB
309" Options that are valid with --build (-B) are:\n"
310" --chunk= -c : chunk size of kibibytes\n"
5787fa49 311" --rounding= : rounding factor for linear array (==chunk size)\n"
e0d19036 312" --level= -l : 0, raid0, or linear\n"
b83d95f3 313" --raid-devices= -n : number of active devices in array\n"
64c4757e
NB
314;
315
316char Help_assemble[] =
9a9dab36
NB
317"Usage: mdadm --assemble device options...\n"
318" mdadm --assemble --scan options...\n"
64c4757e
NB
319"\n"
320"This usage assembles one or more raid arrays from pre-existing\n"
321"components.\n"
e0d19036 322"For each array, mdadm needs to know the md device, the identity of\n"
52826846
NB
323"the array, and a number of sub devices. These can be found in a number\n"
324"of ways.\n"
325"\n"
326"The md device is either given on the command line or is found listed\n"
327"in the config file. The array identity is determined either from the\n"
e0d19036 328"--uuid or --super-minor commandline arguments, from the config file,\n"
52826846 329"or from the first component device on the command line.\n"
64c4757e 330"\n"
52826846
NB
331"The different combinations of these are as follows:\n"
332" If the --scan option is not given, then only devices and identities\n"
333" listed on the command line are considered.\n"
e0d19036 334" The first device will be the array device, and the remainder will be\n"
52826846
NB
335" examined when looking for components.\n"
336" If an explicit identity is given with --uuid or --super-minor, then\n"
e0d19036 337" only devices with a superblock which matches that identity is considered,\n"
52826846 338" otherwise every device listed is considered.\n"
64c4757e 339"\n"
52826846
NB
340" If the --scan option is given, and no devices are listed, then\n"
341" every array listed in the config file is considered for assembly.\n"
e0d19036 342" The identity of candidate devices are determined from the config file.\n"
64c4757e 343"\n"
52826846
NB
344" If the --scan option is given as well as one or more devices, then\n"
345" Those devices are md devices that are to be assembled. Their identity\n"
346" and components are determined from the config file.\n"
64c4757e 347"\n"
e0d19036
NB
348"Options that are valid with --assemble (-A) are:\n"
349" --uuid= -u : uuid of array to assemble. Devices which don't\n"
350" have this uuid are excluded\n"
351" --super-minor= -m : minor number to look for in super-block when\n"
352" choosing devices to use.\n"
353" --config= -c : config file\n"
354" --scan -s : scan config file for missing information\n"
355" --run -R : Try to start the array even if not enough devices\n"
356" for a full array are present\n"
357" --force -f : Assemble the array even if some superblocks appear\n"
358" : out-of-date. This involves modifying the superblocks.\n"
feb716e9 359" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
e0d19036
NB
360;
361
362char Help_manage[] =
363"Usage: mdadm arraydevice options component devices...\n"
364"\n"
365"This usage is for managing the component devices within an array.\n"
366"The --manage option is not needed and is assumed if the first argument\n"
367"is a device name or a management option.\n"
368"The first device listed will be taken to be an md array device, and\n"
369"subsequent devices are (potential) components of that array.\n"
370"\n"
371"Options that are valid with management mode are:\n"
372" --add -a : hotadd subsequent devices to the array\n"
373" --remove -r : remove subsequent devices, which must not be active\n"
374" --fail -f : mark subsequent devices a faulty\n"
375" --set-faulty : same as --fail\n"
376" --run -R : start a partially built array\n"
5787fa49 377" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
378" --readonly -o : mark array as readonly\n"
379" --readwrite -w : mark array as readwrite\n"
380;
381
382char Help_misc[] =
383"Usage: mdadm misc_option devices...\n"
384"\n"
385"This usage is for performing some task on one or more devices, which\n"
386"may be arrays or components, depending on the task.\n"
387"The --misc option is not needed (though it is allowed) and is assumed\n"
388"if the first argument in a misc option.\n"
389"\n"
390"Options that are valid with the miscellaneous mode are:\n"
391" --query -Q : Display general information about how a\n"
392" device relates to the md driver\n"
393" --detail -D : Display details of an array\n"
5787fa49 394" --examine -E : Examine superblock on an array component\n"
e0d19036
NB
395" --zero-superblock : erase the MD superblock from a device.\n"
396" --run -R : start a partially built array\n"
5787fa49 397" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
398" --readonly -o : mark array as readonly\n"
399" --readwrite -w : mark array as readwrite\n"
feb716e9 400" --test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing\n"
e0d19036
NB
401;
402
403char Help_monitor[] =
404"Usage: mdadm --monitor options devices\n"
405"\n"
406"This usage causes mdadm to monitor a number of md arrays by periodically\n"
407"polling their status and acting on any changes.\n"
408"If any devices are listed then those devices are monitored, otherwise\n"
409"all devices listed in the config file are monitored.\n"
410"The address for mailing advisories to, and the program to handle\n"
411"each change can be specified in the config file or on the command line.\n"
412"If no mail address or program are specified, then mdadm reports all\n"
413"state changes to stdout.\n"
414"\n"
dd0781e5 415"Options that are valid with the monitor (-F --follow) mode are:\n"
e0d19036
NB
416" --mail= -m : Address to mail alerts of failure to\n"
417" --program= -p : Program to run when an event is detected\n"
418" --alert= : same as --program\n"
419" --delay= -d : seconds of delay between polling state. default=60\n"
420" --config= -c : specify a different config file\n"
421" --scan -s : find mail-address/program in config file\n"
d013a55e 422" --daemonise -f : Fork and continue in child, parent exits\n"
b5e64645 423" --pid-file= -i : In daemon mode write pid to specified file instead of stdout\n"
aa88f531 424" --oneshot -1 : Check for degraded arrays, then exit\n"
98c6faba 425" --test -t : Generate a TestMessage event against each array at startup\n"
e0d19036
NB
426;
427
dd0781e5
NB
428char Help_grow[] =
429"Usage: mdadm --grow device options\n"
430"\n"
431"This usage causes mdadm to attempt to reconfigure a running array.\n"
432"This is only possibly if the kernel being used supports a particular\n"
433"reconfiguration. This version only supports changing the number of\n"
434"devices in a RAID1, and changing the active size of all devices in\n"
435"a RAID1/4/5/6.\n"
436"\n"
437"Options that are valid with the grow (-F --grow) mode are:\n"
438" --size= -z : Change the active size of devices in an array.\n"
439" : This is useful if all devices have been replaced\n"
440" : with larger devices.\n"
441" --raid-disks= -n : Change the number of active devices in a RAID1\n"
442" : array.\n"
443;
e0d19036
NB
444
445
446
447char Help_config[] =
448"The /etc/mdadm.conf config file:\n\n"
449" The config file contains, apart from blank lines and comment lines that\n"
450" start with a hash(#), four sorts of configuration lines: array lines, \n"
451" device lines, mailaddr lines and program lines.\n"
452" Each configuration line is constructed of a number of space separated\n"
453" words, and can be continued on subsequent physical lines by indenting\n"
454" those lines.\n"
455"\n"
456" A device line starts with the word 'device' and then has a number of words\n"
457" which identify devices. These words should be names of devices in the\n"
458" filesystem, and can contain wildcards. There can be multiple words or each\n"
459" device line, and multiple device lines. All devices so listed are checked\n"
460" for relevant super blocks when assembling arrays.\n"
461"\n"
462" An array line start with the word 'array'. This is followed by the name of\n"
463" the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
464" describe the identity of the array, used to recognise devices to include in the\n"
465" array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
466" as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
467" of devices. This is given as a comma separated list of names, possibly\n"
5787fa49 468" containing wildcards, preceded by 'devices='. If multiple critea are given,\n"
e0d19036
NB
469" than a device must match all of them to be considered.\n"
470"\n"
471" A mailaddr line starts with the word 'mailaddr' and should contain exactly\n"
472" one Email address. 'mdadm --monitor --scan' will send alerts of failed drives\n"
473" to this Email address."
474"\n"
475" A program line starts with the word 'program' and should contain exactly\n"
476" one program name. 'mdadm --monitor --scan' will run this program when any\n"
477" event is detected.\n"
64c4757e
NB
478"\n"
479;
682c7051
NB
480
481
482/* name/number mappings */
483
484mapping_t r5layout[] = {
cd29a5c8
NB
485 { "left-asymmetric", 0},
486 { "right-asymmetric", 1},
487 { "left-symmetric", 2},
488 { "right-symmetric", 3},
682c7051
NB
489
490 { "default", 2},
491 { "la", 0},
492 { "ra", 1},
493 { "ls", 2},
494 { "rs", 3},
495 { NULL, 0}
496};
497
498mapping_t pers[] = {
499 { "linear", -1},
500 { "raid0", 0},
501 { "0", 0},
502 { "stripe", 0},
503 { "raid1", 1},
504 { "1", 1},
505 { "mirror", 1},
506 { "raid4", 4},
507 { "4", 4},
508 { "raid5", 5},
509 { "5", 5},
e0d19036
NB
510 { "multipath", -4},
511 { "mp", -4},
98c6faba
NB
512 { "raid6", 6},
513 { "6", 6},
e5329c37
NB
514 { "raid10", 10},
515 { "10", 10},
b5e64645 516 { "faulty", -5},
682c7051
NB
517 { NULL, 0}
518};
e0d19036
NB
519
520
521mapping_t modes[] = {
522 { "assemble", ASSEMBLE},
523 { "build", BUILD},
524 { "create", CREATE},
525 { "manage", MANAGE},
526 { "misc", MISC},
527 { "monitor", MONITOR},
dd0781e5 528 { "grow", GROW},
e0d19036 529};
b5e64645
NB
530
531mapping_t faultylayout[] = {
532 { "write-transient", WriteTransient },
533 { "wt", WriteTransient },
534 { "read-transient", ReadTransient },
535 { "rt", ReadTransient },
536 { "write-persistent", WritePersistent },
537 { "wp", WritePersistent },
538 { "read-persistent", ReadPersistent },
539 { "rp", ReadPersistent },
540 { "write-all", WriteAll },
541 { "wa", WriteAll },
542 { "read-fixable", ReadFixable },
543 { "rf", ReadFixable },
544
545 { "clear", ClearErrors},
546 { "flush", ClearFaults},
547 { "none", ClearErrors},
548 { "default", ClearErrors},
549 { NULL, 0}
550};