From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
ed.ciechanowski@intel.com, wojciech.neubauer@intel.com
Subject: Re: [PATCH 3/7] FIX: configure disks slot for expansion
Date: Wed, 2 Mar 2011 12:10:01 +1100 [thread overview]
Message-ID: <20110302121001.6a1694dc@notabene.brown> (raw)
In-Reply-To: <20110301145706.10678.63966.stgit@gklab-128-013.igk.intel.com>
On Tue, 01 Mar 2011 15:57:06 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> Some raid_disks that are used for expansion, are not configured yet.
> This is due to earlier set raid_disks limitation.
> Set raid_disks to new (bigger) value and finish disks slot configuration.
>
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
>
> Assemble.c | 15 ++++++++++++++-
> 1 files changed, 14 insertions(+), 1 deletions(-)
>
> diff --git a/Assemble.c b/Assemble.c
> index 6aff049..fa3a0a6 100644
> --- a/Assemble.c
> +++ b/Assemble.c
> @@ -1586,9 +1586,22 @@ int assemble_container_content(struct supertype *st, int mdfd,
> chosen_name, working + preexist);
> if (preexist)
> fprintf(stderr, " (%d new)", working);
> - if (expansion)
> + if (expansion) {
> fprintf(stderr, " ( + %d for expansion)",
> expansion);
> + sysfs_set_num(content, NULL, "raid_disks",
> + content->array.raid_disks + expansion);
> + for (dev = content->devs; dev; dev = dev->next)
> + if (dev->disk.raid_disk >=
> + content->array.raid_disks) {
> + int rv;
> + dprintf("\n\tExpansion: configure slot:"
> + "%i", dev->disk.raid_disk);
> + rv = sysfs_set_num(content, dev, "slot",
> + dev->disk.raid_disk);
> + dprintf(" (status = %i)\n", rv);
> + }
> + }
> fprintf(stderr, "\n");
> }
> if (!err)
I thought I explained how this was suppose to work....
1/ Set the 'old' geometry of the array. sysfs_set_array does this.
2/ Set 'reshape_position'. sysfs_set_array does this.
3/ Set the 'new' geometry of the array. sysfs_set_array should do this but
it doesn't.
4/ Add all the disks. Repeated calls to sysfs_add_disk will do this.
5/ start the array readonly . assemble_container_content calls sysfs_set_str
to do this.
That is all.
NeilBrown
next prev parent reply other threads:[~2011-03-02 1:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 14:56 [PATCH 0/7] Grow_continue, use in assembly (cont.) Adam Kwolek
2011-03-01 14:56 ` [PATCH 1/7] FIX: Verify Backup file name before reshape Adam Kwolek
2011-03-02 1:01 ` NeilBrown
2011-03-02 7:39 ` Kwolek, Adam
2011-03-01 14:56 ` [PATCH 2/7] FIX: reshape in md should wait for monitoring process (external metadata) Adam Kwolek
2011-03-02 1:06 ` NeilBrown
2011-03-01 14:57 ` [PATCH 3/7] FIX: configure disks slot for expansion Adam Kwolek
2011-03-02 1:10 ` NeilBrown [this message]
2011-03-02 7:48 ` Kwolek, Adam
2011-03-01 14:57 ` [PATCH 4/7] Add block_subarray() Adam Kwolek
2011-03-01 14:57 ` [PATCH 5/7] FIX: Block monitor when starting array with reshape in progress Adam Kwolek
2011-03-01 14:57 ` [PATCH 6/7] Continue reshape after assembling array Adam Kwolek
2011-03-01 14:57 ` [PATCH 7/7] FIX: array is frozen after reshape Adam Kwolek
2011-03-02 1:30 ` [PATCH 0/7] Grow_continue, use in assembly (cont.) NeilBrown
2011-03-02 7:49 ` 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=20110302121001.6a1694dc@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 \
--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;
as well as URLs for NNTP newsgroup(s).