From: NeilBrown <neilb@suse.de>
To: "Labun, Marcin" <Marcin.Labun@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Kwolek, Adam" <adam.kwolek@intel.com>
Subject: Re: [PATCH] imsm: fix, the second array need to have the whole available space on devices
Date: Mon, 30 Jan 2012 12:21:46 +1100 [thread overview]
Message-ID: <20120130122146.44866b14@notabene.brown> (raw)
In-Reply-To: <F9123E44003394499FDD2B17C60621D408A87C@IRSMSX101.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Fri, 27 Jan 2012 15:28:36 +0000 "Labun, Marcin" <Marcin.Labun@intel.com>
wrote:
> Fix the case with creating an array with given container in command line
> instead of real devices:
> mdadm -CR /dev/md/raid0 -l 0 -n 2 -z5G /dev/md/imsm
>
> Signed-off-by: Marcin Labun <marcin.labun@intel.com>
> ---
> super-intel.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/super-intel.c b/super-intel.c
> index 0e9269f..03e10bd 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -5525,8 +5525,15 @@ static int reserve_space(struct supertype *st, int raiddisks,
> size /= 2 * chunk;
> size *= 2 * chunk;
> }
> + maxsize = size;
> + }
> + if (!check_env("IMSM_NO_PLATFORM") &&
> + mpb->num_raid_devs > 0 && size && size != maxsize) {
> + fprintf(stderr, Name ": attempting to create a second "
> + "volume with size less then remaining space. "
> + "Aborting...\n");
> + return 0;
> }
> -
> cnt = 0;
> for (dl = super->disks; dl; dl = dl->next)
> if (dl->e)
It is a shame that we need the same test in two different places...
I've applied this patch,
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-01-30 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 15:28 [PATCH] imsm: fix, the second array need to have the whole available space on devices Labun, Marcin
2012-01-30 1:21 ` NeilBrown [this message]
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=20120130122146.44866b14@notabene.brown \
--to=neilb@suse.de \
--cc=Marcin.Labun@intel.com \
--cc=adam.kwolek@intel.com \
--cc=linux-raid@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).