Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "maciej.naruszewicz" <maciej.naruszewicz@intel.com>
To: neilb@suse.de
Cc: wojciech.neubauer@intel.com, adam.kwolek@intel.com,
	krzysztof.wojcik@intel.com, ed.ciechanowski@intel.com,
	linux-raid@vger.kernel.org, dan.j.williams@intel.com
Subject: [PATCH] mdadm.8: Disk coercion with IMSM metadata.
Date: Wed, 13 Jul 2011 12:17:02 +0200	[thread overview]
Message-ID: <20110713101702.26642.74636.stgit@maciek.naruszewicz> (raw)

From: maciej.naruszewicz <maciej.naruszewicz@intel.com>

Actual sizes of disks from different producers may vary,
even though they are claimed to have the same amount of
space. Since creating arrays using IMSM metadata doesn't
support resizing arrays yet, there might be problems when
replacing a disk with a slightly smaller one.

For the time being, disk coercion will not be implemented
for IMSM, however it would be a good idea to inform the
user how to deal with it. Our suggestion is to mention it
in the manual page under the -z option and advise the user
to create arrays using a little less space than the disks
have.

Additionally, the part 'This value can not be used
with CONTAINER metadata such as DDF and IMSM.' was not
clear and was replaced.

Signed-off-by: maciej.naruszewicz <maciej.naruszewicz@intel.com>
---
 mdadm.8.in |   13 ++++++++++---
 1 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/mdadm.8.in b/mdadm.8.in
index 7e8981e..2690e2d 100644
--- a/mdadm.8.in
+++ b/mdadm.8.in
@@ -440,9 +440,16 @@ problems the array can be made bigger again with no loss with another
 .B "\-\-grow \-\-size="
 command.
 
-This value can not be used with
-.B CONTAINER
-metadata such as DDF and IMSM.
+Actual sizes of disks from different manufacturers may slightly differ, even if
+they are said to have the same amount of space. Changing array's size with the 
+.B "\-\-grow \-\-size="
+command is not supported yet by external metadatas such as DDF and IMSM. Creating RAID
+arrays with the
+.B \-z
+option is advised so that the array's size is a bit smaller than the actual maximum
+available data disk's size. Otherwise, replacing a disk in an array with the 'same'
+disk from a different manufacturer is not guaranteed to be always possible due to
+difference in device sizes. 
 
 .TP
 .BR \-Z ", " \-\-array\-size=

---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk

Sad Rejonowy Gdansk Polnoc w Gdansku, 
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego, 
numer KRS 101882

NIP 957-07-52-316
Kapital zakladowy 200.000 zl

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

             reply	other threads:[~2011-07-13 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 10:17 maciej.naruszewicz [this message]
2011-07-14  2:26 ` [PATCH] mdadm.8: Disk coercion with IMSM metadata NeilBrown
2011-07-16  1:10   ` Dan Williams
2011-07-20 12:54     ` Naruszewicz, Maciej
2011-07-26  5:15       ` NeilBrown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110713101702.26642.74636.stgit@maciek.naruszewicz \
    --to=maciej.naruszewicz@intel.com \
    --cc=adam.kwolek@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=krzysztof.wojcik@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=wojciech.neubauer@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox