diff options
author | Adam Kwolek <adam.kwolek@intel.com> | 2011-03-23 11:45:03 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2011-03-23 11:45:03 +1100 |
commit | ca24ddb08da4c86b60f7e049f0b0a2c30b19c95a (patch) | |
tree | 9bda789377bdc7d0254e6e8c6c91522a5144ac39 /mdadm.8.in | |
parent | 7023e0b8aed8807b0c394f61a3c4ac937dbd6b86 (diff) |
man mdadm: add information for MDADM_EXPERIMENTAL flag
Update man for MDADM_EXPERIMENTAL flag.
Minor revisions by Mathias Burén <mathias.buren@gmail.com> and Neil Brown.
Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r-- | mdadm.8.in | 17 |
1 files changed, 17 insertions, 0 deletions
@@ -2229,6 +2229,23 @@ in a container can be converted between levels where those levels are supported by the container, and the conversion is on of those listed above. +Grow functionality (e.g. expand a number of raid devices) for Intel's +IMSM container format has an experimental status. It is guarded by the +.B MDADM_EXPERIMENTAL +environment variable which must be set to '1' for a GROW command to +succeed. +This is for the following reasons: + +.IP 1. +Intel's native IMSM check-pointing is not fully implemented yet. +This causes IMSM incompatibility during the grow process: an array +which is growing cannot roam between Microsoft Windows(R) and Linux +systems. + +.IP 2. +Interrupting a grow operation is not recommended, because it +has not been fully tested for Intel's IMSM container format yet. + .SS SIZE CHANGES Normally when an array is built the "size" is taken from the smallest of the drives. If all the small drives in an arrays are, one at a |