diff options
| author | Adam Kwolek <adam.kwolek@intel.com> | 2011-06-09 05:00:56 +0200 |
|---|---|---|
| committer | NeilBrown <neilb@suse.de> | 2011-06-09 05:00:56 +0200 |
| commit | 0de8d44ddeb80d73dcad8d28cf4c1e779f5c2040 (patch) | |
| tree | 24033d3de4761640c086068cb8093eb41924a990 /mdadm.8.in | |
| parent | imsm: Optimize expansion speed when no backup is required (diff) | |
| download | mdadm-0de8d44ddeb80d73dcad8d28cf4c1e779f5c2040.tar.xz mdadm-0de8d44ddeb80d73dcad8d28cf4c1e779f5c2040.zip | |
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.in | 9 |
1 files changed, 7 insertions, 2 deletions
@@ -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 |