summaryrefslogtreecommitdiff
path: root/mdadm.8.in
diff options
context:
space:
mode:
authorAdam Kwolek <adam.kwolek@intel.com>2011-06-09 13:00:56 +1000
committerNeilBrown <neilb@suse.de>2011-06-09 13:00:56 +1000
commit0de8d44ddeb80d73dcad8d28cf4c1e779f5c2040 (patch)
tree24033d3de4761640c086068cb8093eb41924a990 /mdadm.8.in
parent8016a6d42ecef8bff5b6f9d0020ae549e4324188 (diff)
MAN: Man update for check-pointing
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.in9
1 files changed, 7 insertions, 2 deletions
diff --git a/mdadm.8.in b/mdadm.8.in
index e1d5651d..f549dbf9 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -2225,8 +2225,8 @@ 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
+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.
@@ -2234,6 +2234,11 @@ systems.
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
+.B --backup-file
+option and it is transparent for assembly feature.
+
.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