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