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