diff options
author | NeilBrown <neilb@suse.de> | 2010-12-09 03:06:29 +0100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2010-12-09 03:06:29 +0100 |
commit | 833bb0f8f61c576895a2ec90c344c148c08dadba (patch) | |
tree | a94afa659cd2d01366009d3b0df2c77d473f92f9 /mdadm.8.in | |
parent | Grow: warn if growing an array will make it degraded. (diff) | |
download | mdadm-833bb0f8f61c576895a2ec90c344c148c08dadba.tar.xz mdadm-833bb0f8f61c576895a2ec90c344c148c08dadba.zip |
Allow --update=devicesize with --re-add
This is useful with 1.1 and 1.2 metadata to update the metadata if
the device size has changed.
The same functionality can be achieved by writing to the device size
in sysfs after re-adding normally, but in some cases this might be
easier.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r-- | mdadm.8.in | 9 |
1 files changed, 8 insertions, 1 deletions
@@ -1053,7 +1053,7 @@ will report failure if these specifiers didn't find any match. .BR \-a ", " \-\-add hot-add listed devices. If a device appears to have recently been part of the array -(possibly it failed or was removed) the device is re-added as describe +(possibly it failed or was removed) the device is re\-added as describe in the next point. If that fails or the device was never part of the array, the device is added as a hot-spare. @@ -1079,6 +1079,13 @@ When used on an array that has no metadata (i.e. it was built with it will be assumed that bitmap-based recovery is enough to make the device fully consistent with the array. +When +.B \-\-re\-add +can be accompanied by +.BR \-\-update=devicesize . +See the description of this option when used in Assemble mode for an +explanation of its use. + If the device name given is .B missing then mdadm will try to find any device that looks like it should be |