From: Neil Brown <neilb@suse.de>
To: "Kwolek, Adam" <adam.kwolek@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>
Subject: Re: [md PATCH 1/5] md: Fix: max_disks limit set for external metadata
Date: Wed, 16 Jun 2010 14:50:30 +1000 [thread overview]
Message-ID: <20100616145030.4ed80d70@notabene.brown> (raw)
In-Reply-To: <905EDD02F158D948B186911EB64DB3D11EECE89E@irsmsx503.ger.corp.intel.com>
On Wed, 9 Jun 2010 15:20:37 +0100
"Kwolek, Adam" <adam.kwolek@intel.com> wrote:
> (md: Online Capacity Expansion for IMSM)
> If max_disks limit is not set, md doesn't allow for reconfiguration and starting reshape. For external metadata this limit is not set.
> It is set for native meta during metadata reading.
> Limit max_disks is not used for external meta, so we can set it to value (MD_SB_DISKS) that will not block reshape.
> ---
>
> drivers/md/md.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/md/md.c b/drivers/md/md.c index dfbba92..9cec771 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -5380,6 +5380,8 @@ static int update_raid_disks(mddev_t *mddev, int raid_disks)
> /* change the number of raid disks */
> if (mddev->pers->check_reshape == NULL)
> return -EINVAL;
> + if (mddev->external)
> + mddev->max_disks = MD_SB_DISKS;
> if (raid_disks <= 0 ||
> raid_disks >= mddev->max_disks)
> return -EINVAL;
>
commit 233fca36bb439eadcad28500b5139fed7c64a0ae
should make this unnecessary.
NeilBrown
next prev parent reply other threads:[~2010-06-16 4:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 14:20 [md PATCH 1/5] md: Fix: max_disks limit set for external metadata Kwolek, Adam
2010-06-16 4:50 ` Neil Brown [this message]
2010-06-16 11:25 ` Kwolek, Adam
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=20100616145030.4ed80d70@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@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).