summaryrefslogtreecommitdiffstats
path: root/mdadm.8.in
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-10-04 08:34:21 +0200
committerNeilBrown <neilb@suse.de>2012-10-04 08:34:21 +0200
commit72ca9bcff34d705fde5670a76cee7b85c0033c94 (patch)
treec28be0cf6410e2908e247f9b5b597cc04ac6e09d /mdadm.8.in
parentGrow/raid10: support reducing the devices in a RAID10. (diff)
downloadmdadm-72ca9bcff34d705fde5670a76cee7b85c0033c94.tar.xz
mdadm-72ca9bcff34d705fde5670a76cee7b85c0033c94.zip
Allow data-offset to be specified per-device for create
mdadm --create /dev/md0 .... /dev/sda1:1024 /dev/sdb1:2048 ... The size is in K unless a suffix: K M G is given. The suffix 's' means sectors. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'mdadm.8.in')
-rw-r--r--mdadm.8.in13
1 files changed, 12 insertions, 1 deletions
diff --git a/mdadm.8.in b/mdadm.8.in
index 255b6505..a2d3d00c 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -787,7 +787,7 @@ Since Linux 3.4,
can also be used with
.B --grow
for some RAID levels (initially on RAID10). This allows the
-data-offset to be changed as part of the reshape process. When the
+data\-offset to be changed as part of the reshape process. When the
data offset is changed, no backup file is required as the difference
in offsets is used to provide the same functionality.
@@ -795,6 +795,17 @@ When the new offset is earlier than the old offset, the number of
devices in the array cannot shrink. When it is after the old offset,
the number of devices in the array cannot increase.
+When creating an array,
+.B \-\-data\-offset
+can be specified as
+.BR variable .
+In the case each member device is expected to have a offset appended
+to the name, separated by a colon. This makes it possible to recreate
+exactly an array which has varying data offsets (as can happen when
+different versions of
+.I mdadm
+are used to add different devices).
+
.TP
.BR \-\-continue
This option is complementary to the