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