diff options
author | Dimitri John Ledkov <xnox@ubuntu.com> | 2018-06-26 15:38:57 +0100 |
---|---|---|
committer | Dimitri John Ledkov <xnox@ubuntu.com> | 2018-06-26 15:38:57 +0100 |
commit | 9421e599c44cd50d3df4cd019cd3c53d9320e93d (patch) | |
tree | 2d9606679ad49fbc9f9cf72b3a3a87d7a6dc8fff /mdadm.8.in | |
parent | ec9bfc63255cdf01a67171d1228f562c927c6d36 (diff) |
Cherrypick master patches up to 4th of June 2018.debian/4.1_rc1-3archive/debian/4.1_rc1-3
Diffstat (limited to 'mdadm.8.in')
-rw-r--r-- | mdadm.8.in | 24 |
1 files changed, 6 insertions, 18 deletions
@@ -2718,27 +2718,15 @@ above. Resizing arrays in an IMSM container with .B "--grow --size" is not yet supported. -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 tested yet. -This can 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. - .PP -Note: Intel's native checkpointing doesn't use +Notes: +.IP \(bu 4 +Intel's native checkpointing doesn't use .B --backup-file option and it is transparent for assembly feature. +.IP \(bu 4 +Roaming between Windows(R) and Linux systems for IMSM metadata is not +supported during grow process. .SS SIZE CHANGES Normally when an array is built the "size" is taken from the smallest |