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