2 ''' Copyright Neil Brown and others.
3 ''' This program is free software; you can redistribute it and/or modify
4 ''' it under the terms of the GNU General Public License as published by
5 ''' the Free Software Foundation; either version 2 of the License, or
6 ''' (at your option) any later version.
7 ''' See file COPYING in distribution for details.
10 mdadm \- manage MD devices
16 .BI mdadm " [mode] <raiddevice> [options] <component-devices>"
19 RAID devices are virtual devices created from two or more
20 real block devices. This allows multiple devices (typically disk
21 drives or partitions there-of) to be combined into a single device to
22 hold (for example) a single filesystem.
23 Some RAID levels include redundancy and so can survive some degree of
26 Linux Software RAID devices are implemented through the md (Multiple
27 Devices) device driver.
29 Currently, Linux supports
45 is not a Software RAID mechanism, but does involve
48 each device is a path to one common physical storage device.
51 is also not true RAID, and it only involves one device. It
52 provides a layer over a true device that can be used to inject faults.
55 '''is a program that can be used to create, manage, and monitor
57 '''such it provides a similar set of functionality to the
60 '''The key differences between
67 '''is a single program and not a collection of programs.
70 '''can perform (almost) all of its functions without having a
71 '''configuration file and does not use one by default. Also
73 '''helps with management of the configuration
77 '''can provide information about your arrays (through Query, Detail, and Examine)
87 '''configuration file, at all. It has a different configuration file
88 '''with a different format and a different purpose.
91 mdadm has 7 major modes of operation:
94 Assemble the parts of a previously created
95 array into an active array. Components can be explicitly given
96 or can be searched for.
98 checks that the components
99 do form a bona fide array, and can, on request, fiddle superblock
100 information so as to assemble a faulty array.
104 Build an array that doesn't have per-device superblocks. For these
107 cannot differentiate between initial creation and subsequent assembly
108 of an array. It also cannot perform any checks that appropriate
109 devices have been requested. Because of this, the
111 mode should only be used together with a complete understanding of
116 Create a new array with per-device superblocks.
118 '''in several step create-add-add-run or it can all happen with one command.
121 .B "Follow or Monitor"
122 Monitor one or more md devices and act on any state changes. This is
123 only meaningful for raid1, 4, 5, 6, 10 or multipath arrays as
124 only these have interesting state. raid0 or linear never have
125 missing, spare, or failed drives, so there is nothing to monitor.
129 Grow (or shrink) an array, or otherwise reshape it in some way.
130 Currently supported growth options including changing the active size
131 of component devices in RAID level 1/4/5/6 and changing the number of
132 active devices in RAID1.
136 This is for doing things to specific components of an array such as
137 adding new spares and removing faulty devices.
141 This is an 'everything else' mode that supports operations on active
142 arrays, operations on component devices such as erasing old superblocks, and
143 information gathering operations.
144 '''This mode allows operations on independent devices such as examine MD
145 '''superblocks, erasing old superblocks and stopping active arrays.
149 .SH Options for selecting a mode are:
152 .BR -A ", " --assemble
153 Assemble a pre-existing array.
157 Build a legacy array without superblocks.
164 .BR -F ", " --follow ", " --monitor
171 Change the size or shape of an active array.
173 If a device is given before any options, or if the first option is
178 then the MANAGE mode is assume.
179 Anything other than these will cause the
183 .SH Options that are not mode-specific are:
187 Display general help message or, after one of the above options, a
188 mode specific help message.
192 Display more detailed help about command line parsing and some commonly
196 .BR -V ", " --version
197 Print version information for mdadm.
200 .BR -v ", " --verbose
201 Be more verbose about what is happening. This can be used twice to be
203 The extra verbosity currently only affects
206 .BR "--examine --scan" .
210 Avoid printing purely informative messages. With this,
212 will be silent unless there is something really important to report.
216 Be less verbose. This is used with
224 gives an intermediate level of verbosity.
228 Be more forceful about certain operations. See the various modes of
229 the exact meaning of this option in different contexts.
232 .BR -c ", " --config=
233 Specify the config file. Default is to use
234 .BR /etc/mdadm.conf ,
235 or if that is missing, then
236 .BR /etc/mdadm/mdadm.conf .
237 If the config file given is
239 then nothing will be read, but
241 will act as though the config file contained exactly
242 .B "DEVICE partitions"
245 to find a list of devices to scan.
248 is given for the config file, then
250 will act as though the config file were empty.
256 for missing information.
257 In general, this option gives
259 permission to get any missing information, like component devices,
260 array devices, array identities, and alert destination from the
262 .BR /etc/mdadm.conf .
263 One exception is MISC mode when using
269 says to get a list of array devices from
273 .B -e ", " --metadata=
274 Declare the style of superblock (raid metadata) to be used. The
275 default is 0.90 for --create, and to guess for other operations.
276 The default can be overridden by setting the
285 .IP "0, 0.90, default"
286 Use the original 0.90 format superblock. This format limits arrays to
287 28 componenet devices and limits component devices of levels 1 and
288 greater to 2 terabytes.
289 .IP "1, 1.0, 1.1, 1.2"
290 Use the new version-1 format superblock. This has few restrictions.
291 The different subversion store the superblock at different locations
292 on the device, either at the end (for 1.0), at the start (for 1.1) or
293 4K from the start (for 1.2).
298 This will over-ride any
300 setting in the config file and provides the identify of the host which
301 should be considered the home for any arrays.
303 When creating an array, the
305 will be recorded in the superblock. For version-1 superblocks, it will
306 be prefixed to the array name. For version-0.90 superblocks part of
307 the SHA1 hash of the hostname will be stored in the later half of the
310 When reporting information about an array, any array which is tagged
311 for the given homehost will be reported as such.
313 When using Auto-Assemble, only arrays tagged for the given homehost
316 .SH For create, build, or grow:
319 .BR -n ", " --raid-devices=
320 Specify the number of active devices in the array. This, plus the
321 number of spare devices (see below) must equal the number of
323 (including "\fBmissing\fP" devices)
324 that are listed on the command line for
326 Setting a value of 1 is probably
327 a mistake and so requires that
329 be specified first. A value of 1 will then be allowed for linear,
330 multipath, raid0 and raid1. It is never allowed for raid4 or raid5.
332 This number can only be changed using
334 for RAID1 arrays, and only on kernels which provide necessary support.
337 .BR -x ", " --spare-devices=
338 Specify the number of spare (eXtra) devices in the initial array.
339 Spares can also be added
340 and removed later. The number of component devices listed
341 on the command line must equal the number of raid devices plus the
342 number of spare devices.
347 Amount (in Kibibytes) of space to use from each drive in RAID1/4/5/6.
348 This must be a multiple of the chunk size, and must leave about 128Kb
349 of space at the end of the drive for the RAID superblock.
350 If this is not specified
351 (as it normally is not) the smallest drive (or partition) sets the
352 size, though if there is a variance among the drives of greater than 1%, a warning is
355 This value can be set with
357 for RAID level 1/4/5/6. If the array was created with a size smaller
358 than the currently active drives, the extra space can be accessed
361 The size can be given as
363 which means to choose the largest size that fits on all current drives.
367 Specify chunk size of kibibytes. The default is 64.
371 Specify rounding factor for linear array (==chunk size)
375 Set raid level. When used with
377 options are: linear, raid0, 0, stripe, raid1, 1, mirror, raid4, 4,
378 raid5, 5, raid6, 6, raid10, 10, multipath, mp, faulty. Obviously some of these are synonymous.
382 only linear, stripe, raid0, 0, raid1, multipath, mp, and faulty are valid.
384 Not yet supported with
388 .BR -p ", " --layout=
389 This option configures the fine details of data layout for raid5,
390 and raid10 arrays, and controls the failure modes for
393 The layout of the raid5 parity block can be one of
398 la, ra, ls, rs. The default is left-symmetric.
400 When setting the failure mode for
418 Each mode can be followed by a number which is used as a period
419 between fault generation. Without a number, the fault is generated
420 once on the first relevant request. With a number, the fault will be
421 generated after that many request, and will continue to be generated
422 every time the period elapses.
424 Multiple failure modes can be current simultaneously by using the
425 "--grow" option to set subsequent failure modes.
427 "clear" or "none" will remove any pending or periodic failure modes,
428 and "flush" will clear any persistent faults.
430 To set the parity with "--grow", the level of the array ("faulty")
431 must be specified before the fault mode is specified.
433 Finally, the layout options for RAID10 are one of 'n', 'o' or 'p' followed
434 by a small number. The default is 'n2'.
437 signals 'near' copies. Multiple copies of one data block are at
438 similar offsets in different devices.
441 signals 'offset' copies. Rather than the chunks being duplicated
442 within a stripe, whole stripes are duplicated but are rotated by one
443 device so duplicate blocks are on different devices. Thus subsequent
444 copies of a block are in the next drive, and are one chunk further
449 (multiple copies have very different offsets). See md(4) for more
450 detail about 'near' and 'far'.
452 The number is the number of copies of each datablock. 2 is normal, 3
453 can be useful. This number can be at most equal to the number of
454 devices in the array. It does not need to divide evenly into that
455 number (e.g. it is perfectly legal to have an 'n2' layout for an array
456 with an odd number of devices).
460 same as --layout (thus explaining the p of
464 .BR -b ", " --bitmap=
465 Specify a file to store a write-intent bitmap in. The file should not
466 exist unless --force is also given. The same file should be provided
467 when assembling the array. If the word
469 is given, then the bitmap is stored with the metadata on the array,
470 and so is replicated on all devices. If the word
474 mode, then any bitmap that is present is removed.
476 To help catch typing errors, the filename must contain at least one
477 slash ('/') if it is a real file (not 'internal' or 'none').
479 Note: external bitmaps are only known to work on ext2 and ext3.
480 Storing bitmap files on other filesystems may result in serious problems.
484 Set the chunksize of the bitmap. Each bit corresponds to that many
485 Kilobytes of storage.
486 When using a file based bitmap, the default is to use the smallest
487 size that is atleast 4 and requires no more than 2^21 chunks.
490 bitmap, the chunksize is automatically determined to make best use of
495 .BR -W ", " --write-mostly
496 subsequent devices lists in a
501 command will be flagged as 'write-mostly'. This is valid for RAID1
502 only and means that the 'md' driver will avoid reading from these
503 devices if at all possible. This can be useful if mirroring over a
508 Specify that write-behind mode should be enabled (valid for RAID1
509 only). If an argument is specified, it will set the maximum number
510 of outstanding writes allowed. The default value is 256.
511 A write-intent bitmap is required in order to use write-behind
512 mode, and write-behind is only attempted on drives marked as
519 that the array pre-existed and is known to be clean. It can be useful
520 when trying to recover from a major failure as you can be sure that no
521 data will be affected unless you actually write to the array. It can
522 also be used when creating a RAID1 or RAID10 if you want to avoid the
523 initial resync, however this practice - while normally safe - is not
524 recommended. Use this ony if you really know what you are doing.
528 This is needed when --grow is used to increase the number of
529 raid-devices in a RAID5 if there are no spare devices available.
530 See the section below on RAID_DEVICE CHANGES. The file should be
531 stored on a separate device, not on the raid array being reshaped.
537 for the array. This is currently only effective when creating an
538 array with a version-1 superblock. The name is a simple textual
539 string that can be used to identify array components when assembling.
545 run the array, even if some of the components
546 appear to be active in another array or filesystem. Normally
548 will ask for confirmation before including such components in an
549 array. This option causes that question to be suppressed.
555 accept the geometry and layout specified without question. Normally
557 will not allow creation of an array with only one device, and will try
558 to create a raid5 array with one missing drive (as this makes the
559 initial resync work faster). With
562 will not try to be so clever.
565 .BR -a ", " "--auto{=no,yes,md,mdp,part,p}{NN}"
566 Instruct mdadm to create the device file if needed, possibly allocating
567 an unused minor number. "md" causes a non-partitionable array
568 to be used. "mdp", "part" or "p" causes a partitionable array (2.6 and
569 later) to be used. "yes" requires the named md device to have
570 a 'standard' format, and the type and minor number will be determined
571 from this. See DEVICE NAMES below.
573 The argument can also come immediately after
578 is also given, then any
580 entries in the config file will over-ride the
582 instruction given on the command line.
584 For partitionable arrays,
586 will create the device file for the whole array and for the first 4
587 partitions. A different number of partitions can be specified at the
588 end of this option (e.g.
590 If the device name ends with a digit, the partition names add a 'p',
591 and a number, e.g. "/dev/home1p3". If there is no
592 trailing digit, then the partition names just have a number added,
593 e.g. "/dev/scratch3".
595 If the md device name is in a 'standard' format as described in DEVICE
596 NAMES, then it will be created, if necessary, with the appropriate
597 number based on that name. If the device name is not in one of these
598 formats, then a unused minor number will be allocated. The minor
599 number will be considered unused if there is no active array for that
600 number, and there is no entry in /dev for that number and with a
611 it will also create symlinks from
613 with names starting with
621 to enforce this even if it is suppressing
629 uuid of array to assemble. Devices which don't have this uuid are
633 .BR -m ", " --super-minor=
634 Minor number of device that array was created for. Devices which
635 don't have this minor number are excluded. If you create an array as
636 /dev/md1, then all superblocks will contain the minor number 1, even if
637 the array is later assembled as /dev/md2.
639 Giving the literal word "dev" for
643 to use the minor number of the md device that is being assembled.
647 will look for super blocks with a minor number of 0.
651 Specify the name of the array to assemble. This must be the name
652 that was specified when creating the array. It must either match
653 then name stored in the superblock exactly, or it must match
656 is added to the start of the given name.
660 Assemble the array even if some superblocks appear out-of-date
664 Attempt to start the array even if fewer drives were given than were
665 present last time the array was active. Normally if not all the
666 expected drives are found and
668 is not used, then the array will be assembled but not started.
671 an attempt will be made to start it anyway.
675 This is the reverse of
677 in that it inhibits the started if array unless all expected drives
678 are present. This is only needed with
680 and can be used if you physical connections to devices are
681 not as reliable as you would like.
684 .BR -a ", " "--auto{=no,yes,md,mdp,part}"
685 See this option under Create and Build options.
688 .BR -b ", " --bitmap=
689 Specify the bitmap file that was given when the array was created. If
692 bitmap, there is no need to specify this when assembling the array.
698 was used to grow the number of raid-devices in a RAID5, and the system
699 crashed during the critical section, then the same
701 must be presented to --assemble to allow possibly corrupted data to be
705 .BR -U ", " --update=
706 Update the superblock on each device while assembling the array. The
707 argument given to this flag can be one of
721 option will adjust the superblock of an array what was created on a Sparc
722 machine running a patched 2.2 Linux kernel. This kernel got the
723 alignment of part of the superblock wrong. You can use the
724 .B "--examine --sparc2.2"
727 to see what effect this would have.
731 option will update the
733 field on each superblock to match the minor number of the array being
735 This can be useful if
737 reports a different "Preferred Minor" to
739 In some cases this update will be performed automatically
740 by the kernel driver. In particular the update happens automatically
741 at the first write to an array with redundancy (RAID level 1 or
742 greater) on a 2.6 (or later) kernel.
746 option will change the uuid of the array. If a UUID is given with the
747 "--uuid" option that UUID will be used as a new UUID and will
749 be used to help identify the devices in the array.
750 If no "--uuid" is given, a random uuid is chosen.
754 option will change the
756 of the array as stored in the superblock. This is only supported for
757 version-1 superblocks.
761 option will change the
763 as recorded in the superblock. For version-0 superblocks, this is the
764 same as updating the UUID.
765 For version-1 superblocks, this involves updating the name.
769 option will cause the array to be marked
771 meaning that any redundancy in the array (e.g. parity for raid5,
772 copies for raid1) may be incorrect. This will cause the raid system
773 to perform a "resync" pass to make sure that all redundant information
778 option allows arrays to be moved between machines with different
780 When assembling such an array for the first time after a move, giving
781 .B "--update=byteorder"
784 to expect superblocks to have their byteorder reversed, and will
785 correct that order before assembling the array. This is only valid
786 with original (Version 0.90) superblocks.
790 option will correct the summaries in the superblock. That is the
791 counts of total, working, active, failed, and spare devices.
795 will rarely be of use. It applies to version 1.1 and 1.2 metadata
796 only (where the metadata is at the start of the device) and is only
797 useful when the component device has changed size (typically become
798 larger). The version 1 metadata records the amount of the device that
799 can be used to store data, so if a device in a version 1.1 or 1.2
800 array becomes larger, the metadata will still be visible, but the
801 extra space will not. In this case it might be useful to assemble the
803 .BR --update=devicesize .
806 to determine the maximum usable amount of space on each device and
807 update the relevant field in the metadata.
810 .B --auto-update-homehost
811 This flag is only meaning with auto-assembly (see discussion below).
812 In that situation, if no suitable arrays are found for this homehost,
814 will recan for any arrays at all and will assemble them and update the
815 homehost to match the current host.
821 hot-add listed devices.
825 re-add a device that was recently removed from an array.
829 remove listed devices. They must not be active. i.e. they should
830 be failed or spare devices.
834 mark listed devices as faulty.
841 Each of these options require that the first device list is the array
842 to be acted upon and the remainder are component devices to be added,
843 removed, or marked as fault. Several different operations can be
844 specified for different devices, e.g.
846 mdadm /dev/md0 --add /dev/sda1 --fail /dev/sdb1 --remove /dev/sdb1
848 Each operation applies to all devices listed until the next
851 If an array is using a write-intent bitmap, then devices which have
852 been removed can be re-added in a way that avoids a full
853 reconstruction but instead just updated the blocks that have changed
854 since the device was removed. For arrays with persistent metadata
855 (superblocks) this is done automatically. For arrays created with
857 mdadm needs to be told that this device we removed recently with
860 Devices can only be removed from an array if they are not in active
861 use. i.e. that must be spares or failed devices. To remove an active
862 device, it must be marked as
870 Examine a device to see
871 (1) if it is an md device and (2) if it is a component of an md
873 Information about what is discovered is presented.
877 Print detail of one or more md devices.
880 .BR -E ", " --examine
881 Print content of md superblock on device(s).
884 If an array was created on a 2.2 Linux kernel patched with RAID
885 support, the superblock will have been created incorrectly, or at
886 least incompatibly with 2.4 and later kernels. Using the
890 will fix the superblock before displaying it. If this appears to do
891 the right thing, then the array can be successfully assembled using
892 .BR "--assemble --update=sparc2.2" .
895 .BR -X ", " --examine-bitmap
896 Report information about a bitmap file.
900 start a partially built array.
904 deactivate array, releasing all resources.
907 .BR -o ", " --readonly
908 mark array as readonly.
911 .BR -w ", " --readwrite
912 mark array as readwrite.
916 If the device contains a valid md superblock, the block is
917 over-written with zeros. With
919 the block where the superblock would be is over-written even if it
920 doesn't appear to be valid.
928 is set to reflect the status of the device.
930 .SH For Monitor mode:
933 Give a mail address to send alerts to.
936 .BR -p ", " --program ", " --alert
937 Give a program to be run whenever an event is detected.
941 Cause all events to be reported through 'syslog'. The messages have
942 facility of 'daemon' and varying priorities.
946 Give a delay in seconds.
948 polls the md arrays and then waits this many seconds before polling
949 again. The default is 60 seconds.
952 .BR -f ", " --daemonise
955 to run as a background daemon if it decides to monitor anything. This
956 causes it to fork and run in the child, and to disconnect form the
957 terminal. The process id of the child is written to stdout.
960 which will only continue monitoring if a mail address or alert program
961 is found in the config file.
964 .BR -i ", " --pid-file
967 is running in daemon mode, write the pid of the daemon process to
968 the specified file, instead of printing it on standard output.
971 .BR -1 ", " --oneshot
972 Check arrays only once. This will generate
974 events and more significantly
980 .B " mdadm --monitor --scan -1"
982 from a cron script will ensure regular notification of any degraded arrays.
988 alert for every array found at startup. This alert gets mailed and
989 passed to the alert program. This can be used for testing that alert
990 message do get through successfully.
997 .I md-device options-and-component-devices...
1000 .B mdadm --assemble --scan
1001 .I md-devices-and-options...
1004 .B mdadm --assemble --scan
1008 This usage assembles one or more raid arrays from pre-existing components.
1009 For each array, mdadm needs to know the md device, the identity of the
1010 array, and a number of component-devices. These can be found in a number of ways.
1012 In the first usage example (without the
1014 the first device given is the md device.
1015 In the second usage example, all devices listed are treated as md
1016 devices and assembly is attempted.
1017 In the third (where no devices are listed) all md devices that are
1018 listed in the configuration file are assembled.
1020 If precisely one device is listed, but
1026 was given and identify information is extracted from the configuration file.
1028 The identity can be given with the
1032 option, can be found in the config file, or will be taken from the
1033 super block on the first component-device listed on the command line.
1035 Devices can be given on the
1037 command line or in the config file. Only devices which have an md
1038 superblock which contains the right identity will be considered for
1041 The config file is only used if explicitly named with
1043 or requested with (a possibly implicit)
1051 is not given, then the config file will only be used to find the
1052 identity of md arrays.
1054 Normally the array will be started after it is assembled. However if
1056 is not given and insufficient drives were listed to start a complete
1057 (non-degraded) array, then the array is not started (to guard against
1058 usage errors). To insist that the array be started in this case (as
1059 may work for RAID1, 4, 5, 6, or 10), give the
1065 option is given, either on the command line (--auto) or in the
1066 configuration file (e.g. auto=part), then
1068 will create the md device if necessary or will re-create it if it
1069 doesn't look usable as it is.
1071 This can be useful for handling partitioned devices (which don't have
1072 a stable device number - it can change after a reboot) and when using
1073 "udev" to manage your
1075 tree (udev cannot handle md devices because of the unusual device
1076 initialisation conventions).
1078 If the option to "auto" is "mdp" or "part" or (on the command line
1079 only) "p", then mdadm will create a partitionable array, using the
1080 first free one that is not in use, and does not already have an entry
1081 in /dev (apart from numeric /dev/md* entries).
1083 If the option to "auto" is "yes" or "md" or (on the command line)
1084 nothing, then mdadm will create a traditional, non-partitionable md
1087 It is expected that the "auto" functionality will be used to create
1088 device entries with meaningful names such as "/dev/md/home" or
1089 "/dev/md/root", rather than names based on the numerical array number.
1091 When using this option to create a partitionable array, the device
1092 files for the first 4 partitions are also created. If a different
1093 number is required it can be simply appended to the auto option.
1094 e.g. "auto=part8". Partition names are created by appending a digit
1095 string to the device name, with an intervening "p" if the device name
1100 option is also available in Build and Create modes. As those modes do
1101 not use a config file, the "auto=" config option does not apply to
1109 and no devices are listed,
1111 will first attempt to assemble all the arrays listed in the config
1116 has been specified (either in the config file or on the command line),
1118 will look further for possible arrays and will try to assemble
1119 anything that it finds which is tagged as belonging to the given
1120 homehost. This is the only situation where
1122 will assemble arrays without being given specific device name or
1123 identify information for the array.
1127 finds a consistent set of devices that look like they should comprise
1128 an array, and if the superblock is tagged as belonging to the given
1129 home host, it will automatically choose a device name and try to
1130 assemble the array. If the array uses version-0.90 metadata, then the
1132 number as recorded in the superblock is used to create a name in
1136 If the array uses version-1 metadata, then the
1138 from the superblock is used to similarly create a name in
1140 The name will have any 'host' prefix stripped first.
1144 cannot find any array for the given host at all, and if
1145 .B --auto-update-homehost
1148 will search again for any array (not just an array created for this
1149 host) and will assemble each assuming
1150 .IR --update=homehost .
1151 This will change the host tag in the superblock so that on the next run,
1152 these arrays will be found without the second pass. The intention of
1153 this feature is to support transitioning a set of md arrays to using
1156 The reason for requiring arrays to be tagged with the homehost for
1157 auto assembly is to guard against problems that can arise when moving
1158 devices from one host to another.
1168 .BI --raid-devices= Z
1172 This usage is similar to
1174 The difference is that it creates an array without a superblock. With
1175 these arrays there is no difference between initially creating the array and
1176 subsequently assembling the array, except that hopefully there is useful
1177 data there in the second case.
1179 The level may raid0, linear, multipath, or faulty, or one of their
1180 synonyms. All devices must be listed and the array will be started
1192 .BI --raid-devices= Z
1196 This usage will initialise a new md array, associate some devices with
1197 it, and activate the array.
1201 option is given (as described in more detail in the section on
1202 Assemble mode), then the md device will be created with a suitable
1203 device number if necessary.
1205 As devices are added, they are checked to see if they contain raid
1206 superblocks or filesystems. They are also checked to see if the variance in
1207 device size exceeds 1%.
1209 If any discrepancy is found, the array will not automatically be run, though
1212 can override this caution.
1214 To create a "degraded" array in which some devices are missing, simply
1215 give the word "\fBmissing\fP"
1216 in place of a device name. This will cause
1218 to leave the corresponding slot in the array empty.
1219 For a RAID4 or RAID5 array at most one slot can be
1220 "\fBmissing\fP"; for a RAID6 array at most two slots.
1221 For a RAID1 array, only one real device needs to be given. All of the
1225 When creating a RAID5 array,
1227 will automatically create a degraded array with an extra spare drive.
1228 This is because building the spare into a degraded array is in general faster than resyncing
1229 the parity on a non-degraded, but not clean, array. This feature can
1230 be over-ridden with the
1234 When creating an array with version-1 metadata a name for the host is
1236 If this is not given with the
1240 will chose a name based on the last component of the name of the
1241 device being created. So if
1243 is being created, then the name
1248 is being created, then the name
1254 '''option is given, it is not necessary to list any component-devices in this command.
1255 '''They can be added later, before a
1259 '''is given, the apparent size of the smallest drive given is used.
1261 The General Management options that are valid with --create are:
1264 insist on running the array even if some devices look like they might
1269 start the array readonly - not supported yet.
1277 .I options... devices...
1280 This usage will allow individual devices in an array to be failed,
1281 removed or added. It is possible to perform multiple operations with
1282 on command. For example:
1284 .B " mdadm /dev/md0 -f /dev/hda1 -r /dev/hda1 -a /dev/hda1"
1290 and will then remove it from the array and finally add it back
1291 in as a spare. However only one md array can be affected by a single
1302 MISC mode includes a number of distinct operations that
1303 operate on distinct devices. The operations are:
1306 The device is examined to see if it is
1307 (1) an active md array, or
1308 (2) a component of an md array.
1309 The information discovered is reported.
1313 The device should be an active md device.
1315 will display a detailed description of the array.
1319 will cause the output to be less detailed and the format to be
1320 suitable for inclusion in
1321 .BR /etc/mdadm.conf .
1324 will normally be 0 unless
1326 failed to get useful information about the device(s). However if the
1328 option is given, then the exit status will be:
1332 The array is functioning normally.
1335 The array has at least one failed device.
1338 The array has multiple failed devices and hence is unusable (raid4 or
1342 There was an error while trying to get information about the device.
1347 The device should be a component of an md array.
1349 will read the md superblock of the device and display the contents.
1354 then multiple devices that are components of the one array
1355 are grouped together and reported in a single entry suitable
1357 .BR /etc/mdadm.conf .
1361 without listing any devices will cause all devices listed in the
1362 config file to be examined.
1366 The devices should be active md arrays which will be deactivated, as
1367 long as they are not currently in use.
1371 This will fully activate a partially assembled md array.
1375 This will mark an active array as read-only, providing that it is
1376 not currently being used.
1382 array back to being read/write.
1386 For all operations except
1389 will cause the operation to be applied to all arrays listed in
1394 causes all devices listed in the config file to be examined.
1402 .I options... devices...
1407 to periodically poll a number of md arrays and to report on any events
1410 will never exit once it decides that there are arrays to be checked,
1411 so it should normally be run in the background.
1413 As well as reporting events,
1415 may move a spare drive from one array to another if they are in the
1418 and if the destination array has a failed drive but no spares.
1420 If any devices are listed on the command line,
1422 will only monitor those devices. Otherwise all arrays listed in the
1423 configuration file will be monitored. Further, if
1425 is given, then any other md devices that appear in
1427 will also be monitored.
1429 The result of monitoring the arrays is the generation of events.
1430 These events are passed to a separate program (if specified) and may
1431 be mailed to a given E-mail address.
1433 When passing event to program, the program is run once for each event
1434 and is given 2 or 3 command-line arguments. The first is the
1435 name of the event (see below). The second is the name of the
1436 md device which is affected, and the third is the name of a related
1437 device if relevant, such as a component device that has failed.
1441 is given, then a program or an E-mail address must be specified on the
1442 command line or in the config file. If neither are available, then
1444 will not monitor anything.
1448 will continue monitoring as long as something was found to monitor. If
1449 no program or email is given, then each event is reported to
1452 The different events are:
1456 .B DeviceDisappeared
1457 An md array which previously was configured appears to no longer be
1458 configured. (syslog priority: Critical)
1462 was told to monitor an array which is RAID0 or Linear, then it will
1464 .B DeviceDisappeared
1465 with the extra information
1467 This is because RAID0 and Linear do not support the device-failed,
1468 hot-spare and resync operations which are monitored.
1472 An md array started reconstruction. (syslog priority: Warning)
1478 is 20, 40, 60, or 80, this indicates that rebuild has passed that many
1479 percentage of the total. (syslog priority: Warning)
1483 An md array that was rebuilding, isn't any more, either because it
1484 finished normally or was aborted. (syslog priority: Warning)
1488 An active component device of an array has been marked as
1489 faulty. (syslog priority: Critical)
1493 A spare component device which was being rebuilt to replace a faulty
1494 device has failed. (syslog priority: Critial)
1498 A spare component device which was being rebuilt to replace a faulty
1499 device has been successfully rebuilt and has been made active.
1500 (syslog priority: Info)
1504 A new md array has been detected in the
1506 file. (syslog priority: Info)
1510 A newly noticed array appears to be degraded. This message is not
1513 notices a drive failure which causes degradation, but only when
1515 notices that an array is degraded when it first sees the array.
1516 (syslog priority: Critial)
1520 A spare drive has been moved from one array in a
1522 to another to allow a failed drive to be replaced.
1523 (syslog priority: Info)
1529 has been told, via the config file, that an array should have a certain
1530 number of spare devices, and
1532 detects that it has fewer that this number when it first sees the
1533 array, it will report a
1536 (syslog priority: Warning)
1540 An array was found at startup, and the
1543 (syslog priority: Info)
1553 cause Email to be sent. All events cause the program to be run.
1554 The program is run with two or three arguments, they being the event
1555 name, the array device and possibly a second device.
1557 Each event has an associated array device (e.g.
1559 and possibly a second device. For
1564 the second device is the relevant component device.
1567 the second device is the array that the spare was moved from.
1571 to move spares from one array to another, the different arrays need to
1572 be labelled with the same
1574 in the configuration file. The
1576 name can be any string. It is only necessary that different spare
1577 groups use different names.
1581 detects that an array which is in a spare group has fewer active
1582 devices than necessary for the complete array, and has no spare
1583 devices, it will look for another array in the same spare group that
1584 has a full complement of working drive and a spare. It will then
1585 attempt to remove the spare from the second drive and add it to the
1587 If the removal succeeds but the adding fails, then it is added back to
1591 The GROW mode is used for changing the size or shape of an active
1593 For this to work, the kernel must support the necessary change.
1594 Various types of growth are being added during 2.6 development,
1595 including restructuring a raid5 array to have more active devices.
1597 Currently the only support available is to
1599 change the "size" attribute
1600 for RAID1, RAID5 and RAID6.
1602 increase the "raid-disks" attribute of RAID1 and RAID5.
1604 add a write-intent bitmap to any array which support these bitmaps, or
1605 remove a write-intent bitmap from such an array.
1609 Normally when an array is built the "size" it taken from the smallest
1610 of the drives. If all the small drives in an arrays are, one at a
1611 time, removed and replaced with larger drives, then you could have an
1612 array of large drives with only a small amount used. In this
1613 situation, changing the "size" with "GROW" mode will allow the extra
1614 space to start being used. If the size is increased in this way, a
1615 "resync" process will start to make sure the new parts of the array
1618 Note that when an array changes size, any filesystem that may be
1619 stored in the array will not automatically grow to use the space. The
1620 filesystem will need to be explicitly told to use the extra space.
1622 .SS RAID-DEVICES CHANGES
1624 A RAID1 array can work with any number of devices from 1 upwards
1625 (though 1 is not very useful). There may be times which you want to
1626 increase or decrease the number of active devices. Note that this is
1627 different to hot-add or hot-remove which changes the number of
1630 When reducing the number of devices in a RAID1 array, the slots which
1631 are to be removed from the array must already be vacant. That is, the
1632 devices that which were in those slots must be failed and removed.
1634 When the number of devices is increased, any hot spares that are
1635 present will be activated immediately.
1637 Increasing the number of active devices in a RAID5 is much more
1638 effort. Every block in the array will need to be read and written
1639 back to a new location. From 2.6.17, the Linux Kernel is able to do
1640 this safely, including restart and interrupted "reshape".
1642 When relocating the first few stripes on a raid5, it is not possible
1643 to keep the data on disk completely consistent and crash-proof. To
1644 provide the required safety, mdadm disables writes to the array while
1645 this "critical section" is reshaped, and takes a backup of the data
1646 that is in that section. This backup is normally stored in any spare
1647 devices that the array has, however it can also be stored in a
1648 separate file specified with the
1650 option. If this option is used, and the system does crash during the
1651 critical period, the same file must be passed to
1653 to restore the backup and reassemble the array.
1657 A write-intent bitmap can be added to, or removed from, an active
1658 array. Either internal bitmaps, or bitmaps stored in a separate file
1659 can be added. Note that if you add a bitmap stored in a file which is
1660 in a filesystem that is on the raid array being affected, the system
1661 will deadlock. The bitmap must be on a separate filesystem.
1665 .B " mdadm --query /dev/name-of-device"
1667 This will find out if a given device is a raid array, or is part of
1668 one, and will provide brief information about the device.
1670 .B " mdadm --assemble --scan"
1672 This will assemble and start all arrays listed in the standard config file
1673 file. This command will typically go in a system startup file.
1675 .B " mdadm --stop --scan"
1677 This will shut down all array that can be shut down (i.e. are not
1678 currently in use). This will typically go in a system shutdown script.
1680 .B " mdadm --follow --scan --delay=120"
1682 If (and only if) there is an Email address or program given in the
1683 standard config file, then
1684 monitor the status of all arrays listed in that file by
1685 polling them ever 2 minutes.
1687 .B " mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/hd[ac]1"
1689 Create /dev/md0 as a RAID1 array consisting of /dev/hda1 and /dev/hdc1.
1692 .B " echo 'DEVICE /dev/hd*[0-9] /dev/sd*[0-9]' > mdadm.conf"
1694 .B " mdadm --detail --scan >> mdadm.conf"
1696 This will create a prototype config file that describes currently
1697 active arrays that are known to be made from partitions of IDE or SCSI drives.
1698 This file should be reviewed before being used as it may
1699 contain unwanted detail.
1701 .B " echo 'DEVICE /dev/hd[a-z] /dev/sd*[a-z]' > mdadm.conf"
1703 .B " mdadm --examine --scan --config=mdadm.conf >> mdadm.conf"
1705 This will find what arrays could be assembled from existing IDE and
1706 SCSI whole drives (not partitions) and store the information is the
1707 format of a config file.
1708 This file is very likely to contain unwanted detail, particularly
1711 entries. It should be reviewed and edited before being used as an
1714 .B " mdadm --examine --brief --scan --config=partitions"
1716 .B " mdadm -Ebsc partitions"
1718 Create a list of devices by reading
1719 .BR /proc/partitions ,
1720 scan these for RAID superblocks, and printout a brief listing of all
1723 .B " mdadm -Ac partitions -m 0 /dev/md0"
1725 Scan all partitions and devices listed in
1726 .BR /proc/partitions
1729 out of all such devices with a RAID superblock with a minor number of 0.
1731 .B " mdadm --monitor --scan --daemonise > /var/run/mdadm"
1733 If config file contains a mail address or alert program, run mdadm in
1734 the background in monitor mode monitoring all md devices. Also write
1735 pid of mdadm daemon to
1736 .BR /var/run/mdadm .
1738 .B " mdadm --create --help"
1740 Provide help about the Create mode.
1742 .B " mdadm --config --help"
1744 Provide help about the format of the config file.
1748 Provide general help.
1759 lists all active md devices with information about them.
1761 uses this to find arrays when
1763 is given in Misc mode, and to monitor array reconstruction
1769 The config file lists which devices may be scanned to see if
1770 they contain MD super block, and gives identifying information
1771 (e.g. UUID) about known MD arrays. See
1777 While entries in the /dev directory can have any format you like,
1779 has an understanding of 'standard' formats which it uses to guide its
1780 behaviour when creating device files via the
1784 The standard names for non-partitioned arrays (the only sort of md
1785 array available in 2.4 and earlier) either of
1791 where NN is a number.
1792 The standard names for partitionable arrays (as available from 2.6
1799 Partition numbers should be indicated by added "pMM" to these, thus "/dev/md/d1p2".
1803 was previously known as
1807 is completely separate from the
1809 package, and does not use the
1811 configuration file at all.
1814 For information on the various levels of
1818 .UR http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/
1819 http://ostenfeld.dk/~jakob/Software-RAID.HOWTO/
1822 '''for new releases of the RAID driver check out:
1825 '''.UR ftp://ftp.kernel.org/pub/linux/kernel/people/mingo/raid-patches
1826 '''ftp://ftp.kernel.org/pub/linux/kernel/people/mingo/raid-patches
1831 '''.UR http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/
1832 '''http://www.cse.unsw.edu.au/~neilb/patches/linux-stable/
1835 The latest version of
1837 should always be available from
1839 .UR http://www.kernel.org/pub/linux/utils/raid/mdadm/
1840 http://www.kernel.org/pub/linux/utils/raid/mdadm/
projects / thirdparty / mdadm.git / blob