/*
- * mdctl - manage Linux "md" devices aka RAID arrays.
+ * mdadm - manage Linux "md" devices aka RAID arrays.
*
- * Copyright (C) 2001 Neil Brown <neilb@cse.unsw.edu.au>
+ * Copyright (C) 2001-2002 Neil Brown <neilb@cse.unsw.edu.au>
*
*
* This program is free software; you can redistribute it and/or modify
* Australia
*/
-#include "mdctl.h"
+#include "mdadm.h"
-char Version[] = Name " - v0.5 - 23 August 2001\n";
+char Version[] = Name " - v1.6.0 - 4 June 2004\n";
/*
* File: ReadMe.c
*
* This file contains general comments about the implementation
- * and the various usage messages that can be displayed by mdctl
+ * and the various usage messages that can be displayed by mdadm
*
- * mdctl is a single program that can be used to control Linux md devices.
+ * mdadm is a single program that can be used to control Linux md devices.
* It is intended to provide all the functionality of the mdtools and
* raidtools but with a very different interface.
- * mdctl can perform all functions without a configuration file.
+ * mdadm can perform all functions without a configuration file.
* There is the option of using a configuration file, but not in the same
* way that raidtools uses one
* raidtools uses a configuration file to describe how to create a RAID
* file for such things as stopping a raid array which needs to know
* nothing about the array.
*
- * The configuration file that can be used by mdctl lists two
+ * The configuration file that can be used by mdadm lists two
* different things:
* 1/ a mapping from uuid to md device to identify which arrays are
* expect and what names (numbers) they should be given
*/
/*
- * mdctl has 4 major modes of operation:
+ * mdadm has 7 major modes of operation:
* 1/ Create
- * This mode is used to create a new array with a superbock
+ * This mode is used to create a new array with a superblock
* It can progress in several step create-add-add-run
* or it can all happen with one command
* 2/ Assemble
* This mode is used to assemble the parts of a previously created
* array into an active array. Components can be explicitly given
- * or can be searched for. mdctl (optionally) check that the components
- * do form a bonafide array, and can, on request, fiddle superblock
+ * or can be searched for. mdadm (optionally) check that the components
+ * do form a bona-fide array, and can, on request, fiddle superblock
* version numbers so as to assemble a faulty array.
* 3/ Build
* This is for building legacy arrays without superblocks
* 4/ Manage
- * This is for odd bits an pieces like hotadd, hotremove, setfaulty,
- * stop, readonly,readwrite
- * If an array is only partially setup by the Create/Assemble/Build
- * command, subsequent Manage commands can finish the job.
+ * This is for doing something to one or more devices
+ * in an array, such as add,remove,fail.
+ * run/stop/readonly/readwrite are also available
+ * 5/ Misc
+ * This is for doing things to individual devices.
+ * They might be parts of an array so
+ * zero-superblock, examine might be appropriate
+ * They might be md arrays so
+ * run,stop,rw,ro,detail might be appropriate
+ * Also query will treat it as either
+ * 6/ Monitor
+ * This mode never exits but just monitors arrays and reports changes.
+ * 7/ Grow
+ * This mode allows for changing of key attributes of a raid array, such
+ * as size, number of devices, and possibly even layout.
+ * At the time if writing, there is only minimal support.
*/
-char short_options[]="-ABCDEFhVvc:l:p:m:n:x:u:c:d:z:sarfRSow";
+char short_options[]="-ABCDEFGQhVvbc:l:p:m:n:x:u:c:d:z:U:sa::rfRSow1t";
struct option long_options[] = {
{"manage", 0, 0, '@'},
+ {"misc", 0, 0, '#'},
{"assemble", 0, 0, 'A'},
{"build", 0, 0, 'B'},
{"create", 0, 0, 'C'},
{"detail", 0, 0, 'D'},
{"examine", 0, 0, 'E'},
{"follow", 0, 0, 'F'},
+ {"grow", 0, 0, 'G'},
+ {"zero-superblock", 0, 0, 'K'}, /* deliberately no a short_option */
+ {"query", 0, 0, 'Q'},
/* synonyms */
{"monitor", 0, 0, 'F'},
/* after those will normally come the name of the md device */
{"help", 0, 0, 'h'},
+ {"help-options",0,0,'h'},
{"version", 0, 0, 'V'},
{"verbose", 0, 0, 'v'},
/* For create or build: */
{"chunk", 1, 0, 'c'},
{"rounding", 1, 0, 'c'}, /* for linear, chunk is really a rounding number */
- {"level", 1, 0, 'l'}, /* 0,1,4,5,linear */
- {"parity", 1, 0, 'p'}, /* {left,right}-{a,}symetric */
+ {"level", 1, 0, 'l'}, /* 0,1,4,5,6,linear */
+ {"parity", 1, 0, 'p'}, /* {left,right}-{a,}symmetric */
{"layout", 1, 0, 'p'},
{"raid-disks",1, 0, 'n'},
+ {"raid-devices",1, 0, 'n'},
{"spare-disks",1,0, 'x'},
- {"size" ,1, 0, 'z'},
+ {"spare-devices",1,0, 'x'},
+ {"size", 1, 0, 'z'},
+ {"auto", 2, 0, 'a'}, /* also for --assemble */
+ {"assume-clean",0,0, 3 },
/* For assemble */
{"uuid", 1, 0, 'u'},
{"config", 1, 0, 'c'},
{"scan", 0, 0, 's'},
{"force", 0, 0, 'f'},
+ {"update", 1, 0, 'U'},
/* Management */
{"add", 0, 0, 'a'},
{"remove", 0, 0, 'r'},
{"readonly", 0, 0, 'o'},
{"readwrite", 0, 0, 'w'},
+ /* For Detail/Examine */
+ {"brief", 0, 0, 'b'},
+ {"sparc2.2", 0, 0, 22},
+ {"test", 0, 0, 't'},
+
/* For Follow/monitor */
{"mail", 1, 0, 'm'},
{"program", 1, 0, 'p'},
{"alert", 1, 0, 'p'},
{"delay", 1, 0, 'd'},
-
+ {"daemonise", 0, 0, 'f'},
+ {"daemonize", 0, 0, 'f'},
+ {"oneshot", 0, 0, '1'},
{0, 0, 0, 0}
};
char Usage[] =
-"Usage: mdctl --help\n"
+"Usage: mdadm --help\n"
" for help\n"
;
char Help[] =
-"Usage: mdctl --create device options...\n"
-" mdctl --assemble device options...\n"
-" mdctl --build device options...\n"
-" mdctl --detail device\n"
-" mdctl --examine device\n"
-" mdctl --follow options...\n"
-" mdctl device options...\n"
-" mdctl is used for controlling Linux md devices (aka RAID arrays)\n"
-" For detail help on major modes use, e.g.\n"
-" mdctl --assemble --help\n"
-"\n"
+"Usage: mdadm --create device options...\n"
+" mdadm --assemble device options...\n"
+" mdadm --build device options...\n"
+" mdadm --manage device options...\n"
+" mdadm --misc options... devices\n"
+" mdadm --monitor options...\n"
+" mdadm device options...\n"
+" mdadm is used for building, managing, and monitoring\n"
+" Linux md devices (aka RAID arrays)\n"
+" For detailed help on the above major modes use --help after the mode\n"
+" e.g.\n"
+" mdadm --assemble --help\n"
+" For general help on options use\n"
+" mdadm --help-options\n"
+;
+
+char OptionHelp[] =
"Any parameter that does not start with '-' is treated as a device name\n"
-"The first such name is normally the name of an md device. Subsequent\n"
-"names are names of component devices."
+"The first such name is often the name of an md device. Subsequent\n"
+"names are often names of component devices."
"\n"
-"Available options are:\n"
-" --create -C : Create a new array\n"
-" --assemble -A : Assemble an existing array\n"
-" --build -B : Build a legacy array without superblock\n"
-" --detail -D : Print detail of a given md array\n"
-" --examine -E : Print content of md superblock on device\n"
-" --follow -F : Follow (monitor) any changes to devices and respond to them\n"
-" --monitor : same as --follow\n"
-"\n"
-" --help -h : This help message or, after above option,\n"
+"Some common options are:\n"
+" --help -h : General help message or, after above option,\n"
" mode specific help message\n"
-" --version -V : Print version information for mdctl\n"
+" --help-options : This help message\n"
+" --version -V : Print version information for mdadm\n"
" --verbose -v : Be more verbose about what is happening\n"
+" --brief -b : Be less verbose, more brief\n"
+" --force -f : Override normal checks and be more forceful\n"
+"\n"
+" --assemble -A : Assemble an array\n"
+" --build -B : Build a legacy array\n"
+" --create -C : Create a new array\n"
+" --detail -D : Display details of an array\n"
+" --examine -E : Examine superblock on an array component\n"
+" --monitor -F : monitor (follow) some arrays\n"
+" --query -Q : Display general information about how a\n"
+" device relates to the md driver\n"
+;
+/*
"\n"
" For create or build:\n"
" --chunk= -c : chunk size of kibibytes\n"
-" --rounding= : rounding factor for linear array (==chunck size)\n"
-" --level= -l : raid level: 0,1,4,5,linear. 0 or linear for build\n"
-" --paritiy= -p : raid5 parity algorith: {left,right}-{,a}symmetric\n"
+" --rounding= : rounding factor for linear array (==chunk size)\n"
+" --level= -l : raid level: 0,1,4,5,6,linear,mp. 0 or linear for build\n"
+" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
" --layout= : same as --parity\n"
-" --raid-disks= -n : number of active devices in array\n"
-" --spare-disks= -x : number of spares (eXtras) to allow space for\n"
-" --size= -z : Size (in K) of each drive in RAID1/4/5 - optional\n"
+" --raid-devices= -n : number of active devices in array\n"
+" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
+" --size= -z : Size (in K) of each drive in RAID1/4/5/6 - optional\n"
" --force -f : Honour devices as listed on command line. Don't\n"
" : insert a missing drive for RAID5.\n"
+" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
+" --assume-clean : Assume the array is already in-sync. This is dangerous.\n"
"\n"
" For assemble:\n"
" --uuid= -u : uuid of array to assemble. Devices which don't\n"
" --config= -c : config file\n"
" --scan -s : scan config file for missing information\n"
" --force -f : Assemble the array even if some superblocks appear out-of-date\n"
+" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
+" --auto(=p) -a : Automatically allocate new (partitioned) md array if needed.\n"
+"\n"
+" For detail or examine:\n"
+" --brief -b : Just print device name and UUID\n"
"\n"
" For follow/monitor:\n"
" --mail= -m : Address to mail alerts of failure to\n"
" --fail -f : mark subsequent devices a faulty\n"
" --set-faulty : same as --fail\n"
" --run -R : start a partially built array\n"
-" --stop -S : deactive array, releasing all resources\n"
+" --stop -S : deactivate array, releasing all resources\n"
" --readonly -o : mark array as readonly\n"
" --readwrite -w : mark array as readwrite\n"
+" --zero-superblock : erase the MD superblock from a device.\n"
;
-
+*/
char Help_create[] =
-"Usage: mdctl --create device -chunk=X --level=Y --raid-disks=Z devices\n"
+"Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices\n"
"\n"
-" This usage will initialise a new md array and possibly associate some\n"
-" devices with it. If enough devices are given to complete the array,\n"
-" the array will be activated. Otherwise it will be left inactive\n"
-" to be completed and activated by subsequent management commands.\n"
+" This usage will initialise a new md array, associate some\n"
+" devices with it, and activate the array. In order to create an\n"
+" array with some devices missing, use the special word 'missing' in\n"
+" place of the relevant device name.\n"
"\n"
-" As devices are added, they are checked to see if they contain\n"
-" raid superblocks or filesystems. They are also check to see if\n"
+" Before devices are added, they are checked to see if they already contain\n"
+" raid superblocks or filesystems. They are also checked to see if\n"
" the variance in device size exceeds 1%.\n"
-" If any discrepancy is found, the array will not automatically\n"
-" be run, though the presence of a '--run' can override this\n"
+" If any discrepancy is found, the user will be prompted for confirmation\n"
+" before the array is created. The presence of a '--run' can override this\n"
" caution.\n"
"\n"
-" If the --size option is given, it is not necessary to list any subdevices\n"
-" in this command. They can be added later, before a --run.\n"
+" If the --size option is given then only that many kilobytes of each\n"
+" device is used, no matter how big each device is.\n"
" If no --size is given, the apparent size of the smallest drive given\n"
-" is used.\n"
+" is used for raid level 1 and greater, and the full device is used for\n"
+" other levels.\n"
"\n"
-" The General management options that are valid with --create are:\n"
-" --run : insist of running the array even if not all devices\n"
-" are present or some look odd.\n"
-" --readonly: start the array readonly - not supported yet.\n"
+" Options that are valid with --create (-C) are:\n"
+" --chunk= -c : chunk size of kibibytes\n"
+" --rounding= : rounding factor for linear array (==chunk size)\n"
+" --level= -l : raid level: 0,1,4,5,6,linear,multipath and synonyms\n"
+" --parity= -p : raid5/6 parity algorithm: {left,right}-{,a}symmetric\n"
+" --layout= : same as --parity\n"
+" --raid-devices= -n : number of active devices in array\n"
+" --spare-devices= -x: number of spares (eXtras) devices in initial array\n"
+" --size= -z : Size (in K) of each drive in RAID1/4/5/6 - optional\n"
+" --force -f : Honour devices as listed on command line. Don't\n"
+" : insert a missing drive for RAID5.\n"
+" --run -R : insist of running the array even if not all\n"
+" : devices are present or some look odd.\n"
+" --readonly -o : start the array readonly - not supported yet.\n"
"\n"
;
char Help_build[] =
-"Usage: mdctl --build device -chunk=X --level=Y --raid-disks=Z devices\n"
+"Usage: mdadm --build device -chunk=X --level=Y --raid-devices=Z devices\n"
"\n"
" This usage is similar to --create. The difference is that it creates\n"
-" a legacy array with a superblock. With these arrays there is no\n"
+" a legacy array without a superblock. With these arrays there is no\n"
" different between initially creating the array and subsequently\n"
" assembling the array, except that hopefully there is useful data\n"
" there in the second case.\n"
"\n"
-" The level may only be 0 or linear.\n"
+" The level may only be 0, raid0, or linear.\n"
" All devices must be listed and the array will be started once complete.\n"
+" Options that are valid with --build (-B) are:\n"
+" --chunk= -c : chunk size of kibibytes\n"
+" --rounding= : rounding factor for linear array (==chunk size)\n"
+" --level= -l : 0, raid0, or linear\n"
+" --raid-devices= -n : number of active devices in array\n"
;
char Help_assemble[] =
-"Usage: mdctl --assemble device options...\n"
-" mdctl --assemble --scan options...\n"
+"Usage: mdadm --assemble device options...\n"
+" mdadm --assemble --scan options...\n"
"\n"
"This usage assembles one or more raid arrays from pre-existing\n"
"components.\n"
-"For each array, mdctl needs to know the md device, the identify of\n"
+"For each array, mdadm needs to know the md device, the identity of\n"
"the array, and a number of sub devices. These can be found in a number\n"
"of ways.\n"
"\n"
"The md device is either given on the command line or is found listed\n"
"in the config file. The array identity is determined either from the\n"
-"--uuid or --super-minor commandline arguments, or from the config file,\n"
+"--uuid or --super-minor commandline arguments, from the config file,\n"
"or from the first component device on the command line.\n"
"\n"
"The different combinations of these are as follows:\n"
" If the --scan option is not given, then only devices and identities\n"
" listed on the command line are considered.\n"
-" The first device will be the array devices, and the remainder will\n"
+" The first device will be the array device, and the remainder will be\n"
" examined when looking for components.\n"
" If an explicit identity is given with --uuid or --super-minor, then\n"
-" Each device with a superblock which matches that identity is considered,\n"
+" only devices with a superblock which matches that identity is considered,\n"
" otherwise every device listed is considered.\n"
"\n"
" If the --scan option is given, and no devices are listed, then\n"
" every array listed in the config file is considered for assembly.\n"
-" The identity can candidate devices are determined from the config file.\n"
+" The identity of candidate devices are determined from the config file.\n"
"\n"
" If the --scan option is given as well as one or more devices, then\n"
" Those devices are md devices that are to be assembled. Their identity\n"
" and components are determined from the config file.\n"
"\n"
-"The config file contains, apart from blank lines and comment lines that\n"
-"start with a has, two sorts of configuration lines, array lines and\n"
-"device lines.\n"
-"Each configuration line is constructed of a number of space separated\n"
-"words, and can be continued on subsequent physical lines by indenting\n"
-"those lines.\n"
-"\n"
-"A device line starts with the word 'device' and then has a number of words\n"
-"which identify devices. These words should be names of devices in the filesystem,\n"
-"and can contain wildcards. There can be multiple words or each device line,\n"
-"and multiple device lines. All devices so listed are checked for relevant\n"
-"super blocks when assembling arrays.\n"
-"\n"
-"An array line start with the word 'array'. This is followed by the name of\n"
-"the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
-"describe the identity of the array, used to recognise devices to include in the\n"
-"array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
-"as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
-"of devices. This is given as a comma separated list of names, possibly containing\n"
-"wildcards, preceeded by 'devices='. If multiple critea are given, than a device\n"
-"must match all of them to be considered.\n"
+"Options that are valid with --assemble (-A) are:\n"
+" --uuid= -u : uuid of array to assemble. Devices which don't\n"
+" have this uuid are excluded\n"
+" --super-minor= -m : minor number to look for in super-block when\n"
+" choosing devices to use.\n"
+" --config= -c : config file\n"
+" --scan -s : scan config file for missing information\n"
+" --run -R : Try to start the array even if not enough devices\n"
+" for a full array are present\n"
+" --force -f : Assemble the array even if some superblocks appear\n"
+" : out-of-date. This involves modifying the superblocks.\n"
+" --update= -U : Update superblock: one of sparc2.2, super-minor or summaries\n"
+;
+
+char Help_manage[] =
+"Usage: mdadm arraydevice options component devices...\n"
+"\n"
+"This usage is for managing the component devices within an array.\n"
+"The --manage option is not needed and is assumed if the first argument\n"
+"is a device name or a management option.\n"
+"The first device listed will be taken to be an md array device, and\n"
+"subsequent devices are (potential) components of that array.\n"
+"\n"
+"Options that are valid with management mode are:\n"
+" --add -a : hotadd subsequent devices to the array\n"
+" --remove -r : remove subsequent devices, which must not be active\n"
+" --fail -f : mark subsequent devices a faulty\n"
+" --set-faulty : same as --fail\n"
+" --run -R : start a partially built array\n"
+" --stop -S : deactivate array, releasing all resources\n"
+" --readonly -o : mark array as readonly\n"
+" --readwrite -w : mark array as readwrite\n"
+;
+
+char Help_misc[] =
+"Usage: mdadm misc_option devices...\n"
+"\n"
+"This usage is for performing some task on one or more devices, which\n"
+"may be arrays or components, depending on the task.\n"
+"The --misc option is not needed (though it is allowed) and is assumed\n"
+"if the first argument in a misc option.\n"
+"\n"
+"Options that are valid with the miscellaneous mode are:\n"
+" --query -Q : Display general information about how a\n"
+" device relates to the md driver\n"
+" --detail -D : Display details of an array\n"
+" --examine -E : Examine superblock on an array component\n"
+" --zero-superblock : erase the MD superblock from a device.\n"
+" --run -R : start a partially built array\n"
+" --stop -S : deactivate array, releasing all resources\n"
+" --readonly -o : mark array as readonly\n"
+" --readwrite -w : mark array as readwrite\n"
+" --test -t : exit status 0 if ok, 1 if degrade, 2 if dead, 4 if missing\n"
+;
+
+char Help_monitor[] =
+"Usage: mdadm --monitor options devices\n"
+"\n"
+"This usage causes mdadm to monitor a number of md arrays by periodically\n"
+"polling their status and acting on any changes.\n"
+"If any devices are listed then those devices are monitored, otherwise\n"
+"all devices listed in the config file are monitored.\n"
+"The address for mailing advisories to, and the program to handle\n"
+"each change can be specified in the config file or on the command line.\n"
+"If no mail address or program are specified, then mdadm reports all\n"
+"state changes to stdout.\n"
+"\n"
+"Options that are valid with the monitor (-F --follow) mode are:\n"
+" --mail= -m : Address to mail alerts of failure to\n"
+" --program= -p : Program to run when an event is detected\n"
+" --alert= : same as --program\n"
+" --delay= -d : seconds of delay between polling state. default=60\n"
+" --config= -c : specify a different config file\n"
+" --scan -s : find mail-address/program in config file\n"
+" --daemonise -f : Fork and continue in child, parent exits\n"
+" --oneshot -1 : Check for degraded arrays, then exit\n"
+" --test -t : Generate a TestMessage event against each array at startup\n"
+;
+
+char Help_grow[] =
+"Usage: mdadm --grow device options\n"
+"\n"
+"This usage causes mdadm to attempt to reconfigure a running array.\n"
+"This is only possibly if the kernel being used supports a particular\n"
+"reconfiguration. This version only supports changing the number of\n"
+"devices in a RAID1, and changing the active size of all devices in\n"
+"a RAID1/4/5/6.\n"
+"\n"
+"Options that are valid with the grow (-F --grow) mode are:\n"
+" --size= -z : Change the active size of devices in an array.\n"
+" : This is useful if all devices have been replaced\n"
+" : with larger devices.\n"
+" --raid-disks= -n : Change the number of active devices in a RAID1\n"
+" : array.\n"
+;
+
+
+
+char Help_config[] =
+"The /etc/mdadm.conf config file:\n\n"
+" The config file contains, apart from blank lines and comment lines that\n"
+" start with a hash(#), four sorts of configuration lines: array lines, \n"
+" device lines, mailaddr lines and program lines.\n"
+" Each configuration line is constructed of a number of space separated\n"
+" words, and can be continued on subsequent physical lines by indenting\n"
+" those lines.\n"
+"\n"
+" A device line starts with the word 'device' and then has a number of words\n"
+" which identify devices. These words should be names of devices in the\n"
+" filesystem, and can contain wildcards. There can be multiple words or each\n"
+" device line, and multiple device lines. All devices so listed are checked\n"
+" for relevant super blocks when assembling arrays.\n"
+"\n"
+" An array line start with the word 'array'. This is followed by the name of\n"
+" the array device in the filesystem, e.g. '/dev/md2'. Subsequent words\n"
+" describe the identity of the array, used to recognise devices to include in the\n"
+" array. The identity can be given as a UUID with a word starting 'uuid=', or\n"
+" as a minor-number stored in the superblock using 'super-minor=', or as a list\n"
+" of devices. This is given as a comma separated list of names, possibly\n"
+" containing wildcards, preceded by 'devices='. If multiple critea are given,\n"
+" than a device must match all of them to be considered.\n"
+"\n"
+" A mailaddr line starts with the word 'mailaddr' and should contain exactly\n"
+" one Email address. 'mdadm --monitor --scan' will send alerts of failed drives\n"
+" to this Email address."
+"\n"
+" A program line starts with the word 'program' and should contain exactly\n"
+" one program name. 'mdadm --monitor --scan' will run this program when any\n"
+" event is detected.\n"
"\n"
;
/* name/number mappings */
mapping_t r5layout[] = {
- { "left_asymmetric", 0},
- { "right_asymmetric", 1},
- { "left_symmetric", 2},
- { "right_symmetric", 3},
+ { "left-asymmetric", 0},
+ { "right-asymmetric", 1},
+ { "left-symmetric", 2},
+ { "right-symmetric", 3},
{ "default", 2},
{ "la", 0},
{ "4", 4},
{ "raid5", 5},
{ "5", 5},
+ { "multipath", -4},
+ { "mp", -4},
+ { "raid6", 6},
+ { "6", 6},
{ NULL, 0}
};
+
+
+mapping_t modes[] = {
+ { "assemble", ASSEMBLE},
+ { "build", BUILD},
+ { "create", CREATE},
+ { "manage", MANAGE},
+ { "misc", MISC},
+ { "monitor", MONITOR},
+ { "grow", GROW},
+};
projects / thirdparty / mdadm.git / blobdiff