diff options
Diffstat (limited to 'mdadm.8.in')
| -rw-r--r-- | mdadm.8.in | 107 |
1 files changed, 98 insertions, 9 deletions
@@ -5,7 +5,7 @@ .\" the Free Software Foundation; either version 2 of the License, or .\" (at your option) any later version. .\" See file COPYING in distribution for details. -.TH MDADM 8 "" v3.3 +.TH MDADM 8 "" v3.3.2 .SH NAME mdadm \- manage MD devices .I aka @@ -214,7 +214,10 @@ to detect and assemble arrays \(em possibly in an .P If a device is given before any options, or if the first option is +and of .BR \-\-add , +.BR \-\-re\-add , +.BR \-\-add\-spare , .BR \-\-fail , .BR \-\-remove , or @@ -529,7 +532,7 @@ amount of available space is. .BR \-c ", " \-\-chunk= Specify chunk size of kibibytes. The default when creating an array is 512KB. To ensure compatibility with earlier versions, the -default when Building and array with no persistent metadata is 64KB. +default when building an array with no persistent metadata is 64KB. This is only meaningful for RAID0, RAID4, RAID5, RAID6, and RAID10. RAID4, RAID5, RAID6, and RAID10 require the chunk size to be a power @@ -1083,7 +1086,7 @@ argument given to this flag can be one of .BR devicesize , .BR no\-bitmap , .BR bbl , -.BR no-\bbl , +.BR no\-bbl , .BR metadata , or .BR super\-minor . @@ -1298,6 +1301,15 @@ useful if you are certain that the reason for failure has been resolved. .TP +.B \-\-add\-spare +Add a device as a spare. This is similar to +.B \-\-add +except that it does not attempt +.B \-\-re\-add +first. The device will be added as a spare even if it looks like it +could be an recent member of the array. + +.TP .BR \-r ", " \-\-remove remove listed devices. They must not be active. i.e. they should be failed or spare devices. @@ -1428,13 +1440,30 @@ absolute filepath or a link, e.g. .TP .BR \-Y ", " \-\-export When used with -.B \-\-detail , \-\-detail-platform -or +.BR \-\-detail , +.BR \-\-detail-platform , .BR \-\-examine , +or +.B \-\-incremental output will be formatted as .B key=value pairs for easy import into the environment. +With +.B \-\-incremental +The value +.B MD_STARTED +indicates whether an array was started +.RB ( yes ) +or not, which may include a reason +.RB ( unsafe ", " nothing ", " no ). +Also the value +.B MD_FOREIGN +indicates if the array is expected on this host +.RB ( no ), +or seems to be from elsewhere +.RB ( yes ). + .TP .BR \-E ", " \-\-examine Print contents of the metadata stored on the named device(s). @@ -1559,6 +1588,31 @@ successfully waited. For native arrays this returns immediately as the kernel handles dirty-clean transitions at shutdown. No action is taken if safe-mode handling is disabled. +.TP +.B \-\-action= +Set the "sync_action" for all md devices given to one of +.BR idle , +.BR frozen , +.BR check , +.BR repair . +Setting to +.B idle +will abort any currently running action though some actions will +automatically restart. +Setting to +.B frozen +will abort any current action and ensure no other action starts +automatically. + +Details of +.B check +and +.B repair +can be found it +.IR md (4) +under +.BR "SCRUBBING AND MISMATCHES" . + .SH For Incremental Assembly mode: .TP .BR \-\-rebuild\-map ", " \-r @@ -2334,7 +2388,8 @@ hot-spare and resync operations which are monitored. .TP .B RebuildStarted -An md array started reconstruction. (syslog priority: Warning) +An md array started reconstruction (e.g. recovery, resync, reshape, +check, repair). (syslog priority: Warning) .TP .BI Rebuild NN @@ -2647,6 +2702,7 @@ Usage: .RB [ \-\-run ] .RB [ \-\-quiet ] .I component-device +.RI [ optional-aliases-for-device ] .HP 12 Usage: .B mdadm \-\-incremental \-\-fail @@ -2701,16 +2757,23 @@ That is, is it listed in a .B DEVICES line in that file. If .B DEVICES -is absent then the default it to allow any device. Similar if +is absent then the default it to allow any device. Similarly if .B DEVICES contains the special word .B partitions then any device is allowed. Otherwise the device name given to -.I mdadm +.IR mdadm , +or one of the aliases given, or an alias found in the filesystem, must match one of the names or patterns in a .B DEVICES line. +This is the only context where the aliases are used. They are +usually provided by a +.I udev +rules mentioning +.BR ${DEVLINKS} . + .IP + Does the device have a valid md superblock? If a specific metadata version is requested with @@ -2824,6 +2887,20 @@ to '1', the will create and devices that are needed. .TP +.B MDADM_NO_SYSTEMCTL +If +.I mdadm +detects that +.I systemd +is in use it will normally request +.I systemd +to start various background tasks (particularly +.IR mdmon ) +rather than forking and running them in the background. This can be +suppressed by setting +.BR MDADM_NO_SYSTEMCTL=1 . + +.TP .B IMSM_NO_PLATFORM A key value of IMSM metadata is that it allows interoperability with boot ROMs on Intel platforms, and with other major operating systems. @@ -2840,6 +2917,18 @@ recovery. You should be aware that interoperability may be compromised by setting this value. .TP +.B MDADM_GROW_ALLOW_OLD +If an array is stopped while it is performing a reshape and that +reshape was making use of a backup file, then when the array is +re-assembled +.I mdadm +will sometimes complain that the backup file is too old. If this +happens and you are certain it is the right backup file, you can +over-ride this check by setting +.B MDADM_GROW_ALLOW_OLD=1 +in the environment. + +.TP .B MDADM_CONF_AUTO Any string given in this variable is added to the start of the .B AUTO @@ -3075,7 +3164,7 @@ Partition numbers should be indicated by adding "pMM" to these, thus "/dev/md/d1 From kernel version 2.6.28 the "non-partitioned array" can actually be partitioned. So the "md_d\fBNN\fP" names are no longer needed, and -partitions such as "/dev/md\fBNN\fPp\fBXX\fp" +partitions such as "/dev/md\fBNN\fPp\fBXX\fP" are possible. .PP From kernel version 2.6.29 standard names can be non-numeric following |