]> git.ipfire.org Git - thirdparty/mdadm.git/blame - ReadMe.c
Add nodes option while creating md
[thirdparty/mdadm.git] / ReadMe.c
CommitLineData
64c4757e 1/*
9a9dab36 2 * mdadm - manage Linux "md" devices aka RAID arrays.
64c4757e 3 *
9275a5ec 4 * Copyright (C) 2001-2014 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
b379508e 27#ifndef VERSION
fed12d43 28#define VERSION "3.3.2"
b379508e
N
29#endif
30#ifndef VERS_DATE
fed12d43 31#define VERS_DATE "21st August 2014"
b379508e 32#endif
d56dd607 33char Version[] = "mdadm - v" VERSION " - " VERS_DATE "\n";
4b1ac34b 34
64c4757e
NB
35/*
36 * File: ReadMe.c
37 *
38 * This file contains general comments about the implementation
9a9dab36 39 * and the various usage messages that can be displayed by mdadm
64c4757e 40 *
64c4757e
NB
41 */
42
43/*
dd0781e5 44 * mdadm has 7 major modes of operation:
64c4757e 45 * 1/ Create
5787fa49 46 * This mode is used to create a new array with a superblock
64c4757e
NB
47 * 2/ Assemble
48 * This mode is used to assemble the parts of a previously created
49 * array into an active array. Components can be explicitly given
58380584 50 * or can be searched for. mdadm (optionally) checks that the components
5787fa49 51 * do form a bona-fide array, and can, on request, fiddle superblock
64c4757e
NB
52 * version numbers so as to assemble a faulty array.
53 * 3/ Build
54 * This is for building legacy arrays without superblocks
55 * 4/ Manage
e0d19036
NB
56 * This is for doing something to one or more devices
57 * in an array, such as add,remove,fail.
58 * run/stop/readonly/readwrite are also available
59 * 5/ Misc
60 * This is for doing things to individual devices.
61 * They might be parts of an array so
62 * zero-superblock, examine might be appropriate
63 * They might be md arrays so
64 * run,stop,rw,ro,detail might be appropriate
65 * Also query will treat it as either
66 * 6/ Monitor
67 * This mode never exits but just monitors arrays and reports changes.
dd0781e5
NB
68 * 7/ Grow
69 * This mode allows for changing of key attributes of a raid array, such
70 * as size, number of devices, and possibly even layout.
58380584
N
71 * 8/ Incremental
72 * Is assembles an array incrementally instead of all at once.
73 * As devices are discovered they can be passed to "mdadm --incremental"
74 * which will collect them. When enough devices to for an array are
75 * found, it is started.
64c4757e
NB
76 */
77
866f509f 78char short_options[]="-ABCDEFGIQhVXYWZ:vqbc:i:l:p:m:n:x:u:c:d:z:U:N:sarfRSow1tye:";
024768c4 79char short_bitmap_options[]=
5d500228 80 "-ABCDEFGIQhVXYWZ:vqb:c:i:l:p:m:n:x:u:c:d:z:U:N:sarfRSow1tye:";
8382f19b 81char short_bitmap_auto_options[]=
5d500228 82 "-ABCDEFGIQhVXYWZ:vqb:c:i:l:p:m:n:x:u:c:d:z:U:N:sa:rfRSow1tye:";
773135f5 83
64c4757e 84struct option long_options[] = {
1c7a808c
N
85 {"manage", 0, 0, ManageOpt},
86 {"misc", 0, 0, MiscOpt},
64c4757e
NB
87 {"assemble", 0, 0, 'A'},
88 {"build", 0, 0, 'B'},
89 {"create", 0, 0, 'C'},
90 {"detail", 0, 0, 'D'},
91 {"examine", 0, 0, 'E'},
52826846 92 {"follow", 0, 0, 'F'},
dd0781e5 93 {"grow", 0, 0, 'G'},
8382f19b 94 {"incremental",0,0, 'I'},
f7d3febc 95 {"zero-superblock", 0, 0, KillOpt}, /* deliberately not a short_option */
e0d19036 96 {"query", 0, 0, 'Q'},
c82f047c 97 {"examine-bitmap", 0, 0, 'X'},
1f48664b 98 {"auto-detect", 0, 0, AutoDetect},
4cce4069 99 {"detail-platform", 0, 0, DetailPlatform},
33414a01 100 {"kill-subarray", 1, 0, KillSubarray},
aa534678 101 {"update-subarray", 1, 0, UpdateSubarray},
20b60dcd 102 {"udev-rules", 2, 0, UdevRules},
08ca2adf 103 {"offroot", 0, 0, OffRootOpt},
6d388a88 104 {"examine-badblocks", 0, 0, ExamineBB},
52826846 105
74db60b0
N
106 {"dump", 1, 0, Dump},
107 {"restore", 1, 0, Restore},
108
52826846
NB
109 /* synonyms */
110 {"monitor", 0, 0, 'F'},
aba69144 111
64c4757e 112 /* after those will normally come the name of the md device */
58380584 113
64c4757e 114 {"help", 0, 0, 'h'},
1c7a808c 115 {"help-options",0,0, HelpOptions},
64c4757e
NB
116 {"version", 0, 0, 'V'},
117 {"verbose", 0, 0, 'v'},
dab6685f 118 {"quiet", 0, 0, 'q'},
64c4757e
NB
119
120 /* For create or build: */
1c7a808c
N
121 {"chunk", 1, 0, ChunkSize},
122 {"rounding", 1, 0, ChunkSize}, /* for linear, chunk is really a
123 * rounding number */
98c6faba 124 {"level", 1, 0, 'l'}, /* 0,1,4,5,6,linear */
1c7a808c
N
125 {"parity", 1, 0, Layout}, /* {left,right}-{a,}symmetric */
126 {"layout", 1, 0, Layout},
64c4757e 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'},
1c7a808c 132 {"auto", 1, 0, Auto}, /* also for --assemble */
997aed5d 133 {"assume-clean",0,0, AssumeClean },
f9ce90ba 134 {"metadata", 1, 0, 'e'}, /* superblock format */
1c7a808c 135 {"bitmap", 1, 0, Bitmap},
997aed5d
NB
136 {"bitmap-chunk", 1, 0, BitmapChunk},
137 {"write-behind", 2, 0, WriteBehind},
1c7a808c 138 {"write-mostly",0, 0, WriteMostly},
997aed5d
NB
139 {"re-add", 0, 0, ReAdd},
140 {"homehost", 1, 0, HomeHost},
38098016 141 {"symlinks", 1, 0, Symlinks},
40c9a66a 142 {"data-offset",1, 0, DataOffset},
529e2aa5 143 {"nodes",1, 0, Nodes},
64c4757e
NB
144
145 /* For assemble */
146 {"uuid", 1, 0, 'u'},
1c7a808c 147 {"super-minor",1,0, SuperMinor},
947fd4dd 148 {"name", 1, 0, 'N'},
1c7a808c 149 {"config", 1, 0, ConfigFile},
64c4757e 150 {"scan", 0, 0, 's'},
1c7a808c 151 {"force", 0, 0, Force},
5787fa49 152 {"update", 1, 0, 'U'},
b76b30e0 153 {"freeze-reshape", 0, 0, FreezeReshape},
dfd4d8ee 154
64c4757e 155 /* Management */
1c7a808c 156 {"add", 0, 0, Add},
f33a71f1 157 {"add-spare", 0, 0, AddSpare},
1c7a808c
N
158 {"remove", 0, 0, Remove},
159 {"fail", 0, 0, Fail},
160 {"set-faulty",0, 0, Fail},
70c55e36
N
161 {"replace", 0, 0, Replace},
162 {"with", 0, 0, With},
64c4757e
NB
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 },
1c7a808c 168 {"wait", 0, 0, WaitOpt},
1770662b 169 {"wait-clean", 0, 0, Waitclean },
a740cf64 170 {"action", 1, 0, Action },
52826846 171
cd29a5c8 172 /* For Detail/Examine */
1c7a808c 173 {"brief", 0, 0, Brief},
54bad364 174 {"export", 0, 0, 'Y'},
997aed5d 175 {"sparc2.2", 0, 0, Sparc22},
feb716e9 176 {"test", 0, 0, 't'},
c2ecf5f6 177 {"prefer", 1, 0, Prefer},
cd29a5c8 178
52826846 179 /* For Follow/monitor */
1c7a808c
N
180 {"mail", 1, 0, EMail},
181 {"program", 1, 0, ProgramOpt},
182 {"alert", 1, 0, ProgramOpt},
183 {"increment", 1, 0, Increment},
52826846 184 {"delay", 1, 0, 'd'},
1c7a808c
N
185 {"daemonise", 0, 0, Fork},
186 {"daemonize", 0, 0, Fork},
aa88f531 187 {"oneshot", 0, 0, '1'},
b5e64645 188 {"pid-file", 1, 0, 'i'},
90cf1ddd 189 {"syslog", 0, 0, 'y'},
edde9560
AC
190 {"no-sharing", 0, 0, NoSharing},
191
06b0d786 192 /* For Grow */
997aed5d 193 {"backup-file", 1,0, BackupFile},
87f26d14 194 {"invalid-backup",0,0,InvalidBackup},
84e11361 195 {"array-size", 1, 0, 'Z'},
2dddadb0 196 {"continue", 0, 0, Continue},
8382f19b
NB
197
198 /* For Incremental */
1c7a808c 199 {"rebuild-map", 0, 0, RebuildMapOpt},
950bc344
PC
200 {"path", 1, 0, IncrementalPath},
201
64c4757e
NB
202 {0, 0, 0, 0}
203};
204
205char Usage[] =
9a9dab36 206"Usage: mdadm --help\n"
64c4757e
NB
207" for help\n"
208;
209
210char Help[] =
e5a5d81e
NB
211"mdadm is used for building, managing, and monitoring\n"
212"Linux md devices (aka RAID arrays)\n"
9a9dab36 213"Usage: mdadm --create device options...\n"
e5a5d81e 214" Create a new array from unused devices.\n"
9a9dab36 215" mdadm --assemble device options...\n"
e968ba60 216" Assemble a previously created array.\n"
9a9dab36 217" mdadm --build device options...\n"
e5a5d81e 218" Create or assemble an array without metadata.\n"
e0d19036 219" mdadm --manage device options...\n"
e968ba60 220" make changes to an existing array.\n"
e0d19036 221" mdadm --misc options... devices\n"
e968ba60 222" report on or modify various md related devices.\n"
8382f19b
NB
223" mdadm --grow options device\n"
224" resize/reshape an active array\n"
225" mdadm --incremental device\n"
29ba4804 226" add/remove a device to/from an array as appropriate\n"
e0d19036 227" mdadm --monitor options...\n"
e968ba60 228" Monitor one or more array for significant changes.\n"
9a9dab36 229" mdadm device options...\n"
e968ba60 230" Shorthand for --manage.\n"
e5a5d81e
NB
231"Any parameter that does not start with '-' is treated as a device name\n"
232"or, for --examine-bitmap, a file name.\n"
233"The first such name is often the name of an md device. Subsequent\n"
234"names are often names of component devices.\n"
235"\n"
56eedc1a 236" For detailed help on the above major modes use --help after the mode\n"
e0d19036 237" e.g.\n"
9a9dab36 238" mdadm --assemble --help\n"
56eedc1a
NB
239" For general help on options use\n"
240" mdadm --help-options\n"
241;
242
243char OptionHelp[] =
64c4757e 244"Any parameter that does not start with '-' is treated as a device name\n"
c82f047c 245"or, for --examine-bitmap, a file name.\n"
e0d19036 246"The first such name is often the name of an md device. Subsequent\n"
e5a5d81e 247"names are often names of component devices.\n"
52826846 248"\n"
e0d19036 249"Some common options are:\n"
56eedc1a 250" --help -h : General help message or, after above option,\n"
64c4757e 251" mode specific help message\n"
56eedc1a 252" --help-options : This help message\n"
9a9dab36 253" --version -V : Print version information for mdadm\n"
64c4757e 254" --verbose -v : Be more verbose about what is happening\n"
dab6685f 255" --quiet -q : Don't print un-necessary messages\n"
e0d19036 256" --brief -b : Be less verbose, more brief\n"
e50cf220
MN
257" --export -Y : With --detail, --detail-platform or --examine use\n"
258" key=value format for easy import into environment\n"
e0d19036
NB
259" --force -f : Override normal checks and be more forceful\n"
260"\n"
261" --assemble -A : Assemble an array\n"
e5a5d81e 262" --build -B : Build an array without metadata\n"
e0d19036
NB
263" --create -C : Create a new array\n"
264" --detail -D : Display details of an array\n"
5787fa49 265" --examine -E : Examine superblock on an array component\n"
c82f047c 266" --examine-bitmap -X: Display the detail of a bitmap file\n"
6d388a88 267" --examine-badblocks: Display list of known bad blocks on device\n"
e0d19036 268" --monitor -F : monitor (follow) some arrays\n"
8382f19b 269" --grow -G : resize/ reshape and array\n"
29ba4804 270" --incremental -I : add/remove a single device to/from an array as appropriate\n"
e0d19036
NB
271" --query -Q : Display general information about how a\n"
272" device relates to the md driver\n"
1f48664b 273" --auto-detect : Start arrays auto-detected by the kernel\n"
e0d19036
NB
274;
275/*
64c4757e
NB
276"\n"
277" For create or build:\n"
c82f047c 278" --bitmap= -b : File to store bitmap in - may pre-exist for --build\n"
64c4757e 279" --chunk= -c : chunk size of kibibytes\n"
5787fa49 280" --rounding= : rounding factor for linear array (==chunk size)\n"
58380584
N
281" --level= -l : raid level: 0,1,4,5,6,10,linear, or mp for create.\n"
282" : 0,1,10,mp,faulty or linear for build.\n"
98c6faba 283" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
58380584 284" --layout= : same as --parity, for RAID10: [fno]NN \n"
b83d95f3 285" --raid-devices= -n : number of active devices in array\n"
58380584 286" --spare-devices= -x: number of spare (eXtra) devices in initial array\n"
e5329c37 287" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
52826846
NB
288" --force -f : Honour devices as listed on command line. Don't\n"
289" : insert a missing drive for RAID5.\n"
58380584 290" --assume-clean : Assume the array is already in-sync. This is dangerous for RAID5.\n"
c82f047c
NB
291" --bitmap-chunk= : chunksize of bitmap in bitmap file (Kilobytes)\n"
292" --delay= -d : seconds between bitmap updates\n"
dfd4d8ee 293" --write-behind= : number of simultaneous write-behind requests to allow (requires bitmap)\n"
947fd4dd 294" --name= -N : Textual name for array - max 32 characters\n"
64c4757e
NB
295"\n"
296" For assemble:\n"
c82f047c 297" --bitmap= -b : File to find bitmap information in\n"
64c4757e
NB
298" --uuid= -u : uuid of array to assemble. Devices which don't\n"
299" have this uuid are excluded\n"
52826846
NB
300" --super-minor= -m : minor number to look for in super-block when\n"
301" choosing devices to use.\n"
947fd4dd 302" --name= -N : Array name to look for in super-block.\n"
64c4757e
NB
303" --config= -c : config file\n"
304" --scan -s : scan config file for missing information\n"
305" --force -f : Assemble the array even if some superblocks appear out-of-date\n"
cbfbcb0b 306" --update= -U : Update superblock: try '-A --update=?' for list of options.\n"
b8a8ccf9 307" --no-degraded : Do not start any degraded arrays - default unless --scan.\n"
64c4757e 308"\n"
cd29a5c8
NB
309" For detail or examine:\n"
310" --brief -b : Just print device name and UUID\n"
311"\n"
52826846
NB
312" For follow/monitor:\n"
313" --mail= -m : Address to mail alerts of failure to\n"
314" --program= -p : Program to run when an event is detected\n"
315" --alert= : same as --program\n"
316" --delay= -d : seconds of delay between polling state. default=60\n"
317"\n"
64c4757e
NB
318" General management:\n"
319" --add -a : add, or hotadd subsequent devices\n"
58380584 320" --re-add : re-add a recently removed device\n"
64c4757e 321" --remove -r : remove subsequent devices\n"
58380584 322" --fail -f : mark subsequent devices as faulty\n"
64c4757e 323" --set-faulty : same as --fail\n"
70c55e36 324" --replace : mark a device for replacement\n"
64c4757e 325" --run -R : start a partially built array\n"
5787fa49 326" --stop -S : deactivate array, releasing all resources\n"
64c4757e
NB
327" --readonly -o : mark array as readonly\n"
328" --readwrite -w : mark array as readwrite\n"
9a9dab36 329" --zero-superblock : erase the MD superblock from a device.\n"
b90c0e9a 330" --wait -W : wait for recovery/resync/reshape to finish.\n"
64c4757e 331;
e0d19036 332*/
64c4757e
NB
333
334char Help_create[] =
b83d95f3 335"Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e 336"\n"
aa88f531
NB
337" This usage will initialise a new md array, associate some\n"
338" devices with it, and activate the array. In order to create an\n"
339" array with some devices missing, use the special word 'missing' in\n"
340" place of the relevant device name.\n"
64c4757e 341"\n"
aa88f531 342" Before devices are added, they are checked to see if they already contain\n"
e0d19036 343" raid superblocks or filesystems. They are also checked to see if\n"
64c4757e 344" the variance in device size exceeds 1%.\n"
aa88f531
NB
345" If any discrepancy is found, the user will be prompted for confirmation\n"
346" before the array is created. The presence of a '--run' can override this\n"
64c4757e
NB
347" caution.\n"
348"\n"
e0d19036
NB
349" If the --size option is given then only that many kilobytes of each\n"
350" device is used, no matter how big each device is.\n"
682c7051 351" If no --size is given, the apparent size of the smallest drive given\n"
e0d19036
NB
352" is used for raid level 1 and greater, and the full device is used for\n"
353" other levels.\n"
682c7051 354"\n"
e0d19036 355" Options that are valid with --create (-C) are:\n"
c82f047c 356" --bitmap= : Create a bitmap for the array with the given filename\n"
58380584
N
357" : or an internal bitmap is 'internal' is given\n"
358" --chunk= -c : chunk size in kibibytes\n"
5787fa49 359" --rounding= : rounding factor for linear array (==chunk size)\n"
58380584 360" --level= -l : raid level: 0,1,4,5,6,10,linear,multipath and synonyms\n"
98c6faba 361" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
58380584 362" --layout= : same as --parity, for RAID10: [fno]NN \n"
b83d95f3 363" --raid-devices= -n : number of active devices in array\n"
58380584 364" --spare-devices= -x: number of spare (eXtra) devices in initial array\n"
e5329c37 365" --size= -z : Size (in K) of each drive in RAID1/4/5/6/10 - optional\n"
40c9a66a
N
366" --data-offset= : Space to leave between start of device and start\n"
367" : of array data.\n"
e0d19036
NB
368" --force -f : Honour devices as listed on command line. Don't\n"
369" : insert a missing drive for RAID5.\n"
aa88f531 370" --run -R : insist of running the array even if not all\n"
e0d19036 371" : devices are present or some look odd.\n"
aa88f531 372" --readonly -o : start the array readonly - not supported yet.\n"
947fd4dd 373" --name= -N : Textual name for array - max 32 characters\n"
c82f047c
NB
374" --bitmap-chunk= : bitmap chunksize in Kilobytes.\n"
375" --delay= -d : bitmap update delay in seconds.\n"
64c4757e
NB
376"\n"
377;
378
379char Help_build[] =
b83d95f3 380"Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices\n"
64c4757e
NB
381"\n"
382" This usage is similar to --create. The difference is that it creates\n"
e0d19036 383" a legacy array without a superblock. With these arrays there is no\n"
64c4757e
NB
384" different between initially creating the array and subsequently\n"
385" assembling the array, except that hopefully there is useful data\n"
386" there in the second case.\n"
387"\n"
58380584 388" The level may only be 0, 1, 10, linear, multipath, or faulty.\n"
64c4757e 389" All devices must be listed and the array will be started once complete.\n"
e0d19036 390" Options that are valid with --build (-B) are:\n"
c82f047c 391" --bitmap= : file to store/find bitmap information in.\n"
e0d19036 392" --chunk= -c : chunk size of kibibytes\n"
5787fa49 393" --rounding= : rounding factor for linear array (==chunk size)\n"
58380584 394" --level= -l : 0, 1, 10, linear, multipath, faulty\n"
c82f047c
NB
395" --raid-devices= -n : number of active devices in array\n"
396" --bitmap-chunk= : bitmap chunksize in Kilobytes.\n"
397" --delay= -d : bitmap update delay in seconds.\n"
64c4757e
NB
398;
399
400char Help_assemble[] =
9a9dab36
NB
401"Usage: mdadm --assemble device options...\n"
402" mdadm --assemble --scan options...\n"
64c4757e
NB
403"\n"
404"This usage assembles one or more raid arrays from pre-existing\n"
405"components.\n"
e0d19036 406"For each array, mdadm needs to know the md device, the identity of\n"
52826846
NB
407"the array, and a number of sub devices. These can be found in a number\n"
408"of ways.\n"
409"\n"
58380584
N
410"The md device is given on the command line, is found listed in the\n"
411"config file, or can be deduced from the array identity.\n"
412"The array identity is determined either from the --uuid, --name, or\n"
413"--super-minor commandline arguments, from the config file,\n"
52826846 414"or from the first component device on the command line.\n"
64c4757e 415"\n"
52826846
NB
416"The different combinations of these are as follows:\n"
417" If the --scan option is not given, then only devices and identities\n"
418" listed on the command line are considered.\n"
e0d19036 419" The first device will be the array device, and the remainder will be\n"
52826846
NB
420" examined when looking for components.\n"
421" If an explicit identity is given with --uuid or --super-minor, then\n"
e0d19036 422" only devices with a superblock which matches that identity is considered,\n"
52826846 423" otherwise every device listed is considered.\n"
64c4757e 424"\n"
52826846
NB
425" If the --scan option is given, and no devices are listed, then\n"
426" every array listed in the config file is considered for assembly.\n"
e0d19036 427" The identity of candidate devices are determined from the config file.\n"
58380584
N
428" After these arrays are assembled, mdadm will look for other devices\n"
429" that could form further arrays and tries to assemble them. This can\n"
430" be disabled using the 'AUTO' option in the config file.\n"
64c4757e 431"\n"
52826846
NB
432" If the --scan option is given as well as one or more devices, then\n"
433" Those devices are md devices that are to be assembled. Their identity\n"
434" and components are determined from the config file.\n"
64c4757e 435"\n"
b8a8ccf9
NB
436" If mdadm can not find all of the components for an array, it will assemble\n"
437" it but not activate it unless --run or --scan is given. To preserve this\n"
438" behaviour even with --scan, add --no-degraded. Note that \"all of the\n"
439" components\" means as many as were present the last time the array was running\n"
440" as recorded in the superblock. If the array was already degraded, and\n"
441" the missing device is not a new problem, it will still be assembled. It\n"
442" is only newly missing devices that cause the array not to be started.\n"
443"\n"
e0d19036 444"Options that are valid with --assemble (-A) are:\n"
58380584 445" --bitmap= : bitmap file to use with the array\n"
e0d19036
NB
446" --uuid= -u : uuid of array to assemble. Devices which don't\n"
447" have this uuid are excluded\n"
448" --super-minor= -m : minor number to look for in super-block when\n"
449" choosing devices to use.\n"
947fd4dd 450" --name= -N : Array name to look for in super-block.\n"
e0d19036
NB
451" --config= -c : config file\n"
452" --scan -s : scan config file for missing information\n"
453" --run -R : Try to start the array even if not enough devices\n"
454" for a full array are present\n"
455" --force -f : Assemble the array even if some superblocks appear\n"
456" : out-of-date. This involves modifying the superblocks.\n"
cbfbcb0b 457" --update= -U : Update superblock: try '-A --update=?' for option list.\n"
b8a8ccf9 458" --no-degraded : Assemble but do not start degraded arrays.\n"
0ea8f5b1 459" --readonly -o : Mark the array as read-only. No resync will start.\n"
e0d19036
NB
460;
461
462char Help_manage[] =
463"Usage: mdadm arraydevice options component devices...\n"
464"\n"
465"This usage is for managing the component devices within an array.\n"
466"The --manage option is not needed and is assumed if the first argument\n"
467"is a device name or a management option.\n"
58380584 468"The first device listed will be taken to be an md array device, any\n"
e0d19036
NB
469"subsequent devices are (potential) components of that array.\n"
470"\n"
471"Options that are valid with management mode are:\n"
472" --add -a : hotadd subsequent devices to the array\n"
58380584
N
473" --re-add : subsequent devices are re-added if there were\n"
474" : recent members of the array\n"
e0d19036
NB
475" --remove -r : remove subsequent devices, which must not be active\n"
476" --fail -f : mark subsequent devices a faulty\n"
477" --set-faulty : same as --fail\n"
70c55e36
N
478" --replace : mark device(s) to be replaced by spares. Once\n"
479" : replacement completes, device will be marked faulty\n"
480" --with : Indicate which spare a previous '--replace' should\n"
481" : prefer to use\n"
e0d19036 482" --run -R : start a partially built array\n"
5787fa49 483" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
484" --readonly -o : mark array as readonly\n"
485" --readwrite -w : mark array as readwrite\n"
486;
487
488char Help_misc[] =
489"Usage: mdadm misc_option devices...\n"
490"\n"
491"This usage is for performing some task on one or more devices, which\n"
492"may be arrays or components, depending on the task.\n"
493"The --misc option is not needed (though it is allowed) and is assumed\n"
494"if the first argument in a misc option.\n"
495"\n"
496"Options that are valid with the miscellaneous mode are:\n"
497" --query -Q : Display general information about how a\n"
498" device relates to the md driver\n"
499" --detail -D : Display details of an array\n"
4cce4069 500" --detail-platform : Display hardware/firmware details\n"
5787fa49 501" --examine -E : Examine superblock on an array component\n"
c82f047c 502" --examine-bitmap -X: Display contents of a bitmap file\n"
6d388a88 503" --examine-badblocks: Display list of known bad blocks on device\n"
e0d19036
NB
504" --zero-superblock : erase the MD superblock from a device.\n"
505" --run -R : start a partially built array\n"
5787fa49 506" --stop -S : deactivate array, releasing all resources\n"
e0d19036
NB
507" --readonly -o : mark array as readonly\n"
508" --readwrite -w : mark array as readwrite\n"
feb716e9 509" --test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing\n"
b90c0e9a 510" --wait -W : wait for resync/rebuild/recovery to finish\n"
a740cf64 511" --action= : initiate or abort ('idle' or 'frozen') a 'check' or 'repair'.\n"
e0d19036
NB
512;
513
514char Help_monitor[] =
515"Usage: mdadm --monitor options devices\n"
516"\n"
517"This usage causes mdadm to monitor a number of md arrays by periodically\n"
518"polling their status and acting on any changes.\n"
519"If any devices are listed then those devices are monitored, otherwise\n"
520"all devices listed in the config file are monitored.\n"
521"The address for mailing advisories to, and the program to handle\n"
522"each change can be specified in the config file or on the command line.\n"
58380584
N
523"There must be at least one destination for advisories, whether\n"
524"an email address, a program, or --syslog\n"
e0d19036 525"\n"
dd0781e5 526"Options that are valid with the monitor (-F --follow) mode are:\n"
e0d19036
NB
527" --mail= -m : Address to mail alerts of failure to\n"
528" --program= -p : Program to run when an event is detected\n"
529" --alert= : same as --program\n"
237d8790 530" --syslog -y : Report alerts via syslog\n"
9a36a9b7 531" --increment= -r : Report RebuildNN events in the given increment. default=20\n"
e0d19036
NB
532" --delay= -d : seconds of delay between polling state. default=60\n"
533" --config= -c : specify a different config file\n"
534" --scan -s : find mail-address/program in config file\n"
d013a55e 535" --daemonise -f : Fork and continue in child, parent exits\n"
b5e64645 536" --pid-file= -i : In daemon mode write pid to specified file instead of stdout\n"
aa88f531 537" --oneshot -1 : Check for degraded arrays, then exit\n"
98c6faba 538" --test -t : Generate a TestMessage event against each array at startup\n"
e0d19036
NB
539;
540
dd0781e5
NB
541char Help_grow[] =
542"Usage: mdadm --grow device options\n"
543"\n"
544"This usage causes mdadm to attempt to reconfigure a running array.\n"
545"This is only possibly if the kernel being used supports a particular\n"
58380584 546"reconfiguration.\n"
dd0781e5 547"\n"
891d2994 548"Options that are valid with the grow (-G --grow) mode are:\n"
58380584 549" --level= -l : Tell mdadm what level to convert the array to.\n"
00be0b12 550" --layout= -p : For a FAULTY array, set/change the error mode.\n"
58380584 551" : for other arrays, update the layout\n"
dd0781e5
NB
552" --size= -z : Change the active size of devices in an array.\n"
553" : This is useful if all devices have been replaced\n"
0083584d
N
554" : with larger devices. Value is in Kilobytes, or\n"
555" : the special word 'max' meaning 'as large as possible'.\n"
58380584
N
556" --assume-clean : When increasing the --size, this flag will avoid\n"
557" : a resync of the new space\n"
558" --chunk= -c : Change the chunksize of the array\n"
e5669f40 559" --raid-devices= -n : Change the number of active devices in an array.\n"
58380584
N
560" --add= -a : Add listed devices as part of reshape. This is\n"
561" : needed for resizing a RAID0 which cannot have\n"
562" : spares already present.\n"
00be0b12 563" --bitmap= -b : Add or remove a write-intent bitmap.\n"
58380584 564" --backup-file= file : A file on a different device to store data for a\n"
e5669f40 565" : short time while increasing raid-devices on a\n"
58380584
N
566" : RAID4/5/6 array. Also needed throughout a reshape\n"
567" : when changing parameters other than raid-devices\n"
84e11361
N
568" --array-size= -Z : Change visible size of array. This does not change\n"
569" : any data on the device, and is not stable across restarts.\n"
40c9a66a 570" --data-offset= : Location on device to move start of data to.\n"
dd0781e5 571;
e0d19036 572
8382f19b 573char Help_incr[] =
29ba4804 574"Usage: mdadm --incremental [-Rqrsf] device\n"
8382f19b
NB
575"\n"
576"This usage allows for incremental assembly of md arrays. Devices can be\n"
577"added one at a time as they are discovered. Once an array has all expected\n"
578"devices, it will be started.\n"
579"\n"
29ba4804
N
580"Optionally, the process can be reversed by using the fail option.\n"
581"When fail mode is invoked, mdadm will see if the device belongs to an array\n"
582"and then both fail (if needed) and remove the device from that array.\n"
583"\n"
584"Options that are valid with incremental assembly (-I --incremental) are:\n"
585" --run -R : Run arrays as soon as a minimal number of devices are\n"
7e6140e6
N
586" : present rather than waiting for all expected.\n"
587" --quiet -q : Don't print any information messages, just errors.\n"
588" --rebuild-map -r : Rebuild the 'map' file that mdadm uses for tracking\n"
589" : partial arrays.\n"
590" --scan -s : Use with -R to start any arrays that have the minimal\n"
591" : required number of devices, but are not yet started.\n"
58380584
N
592" --fail -f : First fail (if needed) and then remove device from\n"
593" : any array that it is a member of.\n"
8382f19b 594;
e0d19036
NB
595
596char Help_config[] =
597"The /etc/mdadm.conf config file:\n\n"
598" The config file contains, apart from blank lines and comment lines that\n"
58380584
N
599" start with a hash(#), array lines, device lines, and various\n"
600" configuration lines.\n"
601" Each line is constructed of a number of space separated words, and can\n"
602" be continued on subsequent physical lines by indenting those lines.\n"
e0d19036
NB
603"\n"
604" A device line starts with the word 'device' and then has a number of words\n"
605" which identify devices. These words should be names of devices in the\n"
606" filesystem, and can contain wildcards. There can be multiple words or each\n"
607" device line, and multiple device lines. All devices so listed are checked\n"
608" for relevant super blocks when assembling arrays.\n"
609"\n"
610" An array line start with the word 'array'. This is followed by the name of\n"
611" the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
612" describe the identity of the array, used to recognise devices to include in the\n"
613" array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
614" as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
615" of devices. This is given as a comma separated list of names, possibly\n"
5787fa49 616" containing wildcards, preceded by 'devices='. If multiple critea are given,\n"
e0d19036
NB
617" than a device must match all of them to be considered.\n"
618"\n"
58380584
N
619" Other configuration lines include:\n"
620" mailaddr, mailfrom, program used for --monitor mode\n"
621" create, auto used when creating device names in /dev\n"
622" homehost, policy, part-policy used to guide policy in various\n"
623" situations\n"
64c4757e
NB
624"\n"
625;
682c7051 626
5187a385
N
627char *mode_help[mode_count] = {
628 [0] = Help,
629 [ASSEMBLE] = Help_assemble,
630 [BUILD] = Help_build,
631 [CREATE] = Help_create,
632 [MANAGE] = Help_manage,
633 [MISC] = Help_misc,
634 [MONITOR] = Help_monitor,
635 [GROW] = Help_grow,
636 [INCREMENTAL] = Help_incr,
637};