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 0/6] OLCE raid5/0 (all arrays in container)
Date: Mon, 17 Jan 2011 12:31:07 +1100 [thread overview]
Message-ID: <20110117123107.58d1024e@notabene.brown> (raw)
In-Reply-To: <20110113144252.12728.82642.stgit@gklab-128-013.igk.intel.com>
On Thu, 13 Jan 2011 15:50:02 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> The following series adds possibility to reshape all (raid0/5) arrays in container for expansion feature.
> The main problem resolved in this series is how initialize second (and next) raid0 reshapes for container reshape
> executed as set of array reshapes.
>
> For i.e. second raid0 array mdmon should initialize metadata to let know to mdadm that there is something more to reshape.
> But problem is what to do when mdmon is not loaded? (for first raid0 array this is not a problem, reshape_super() in mdadm updates metadata).
>
> this is resolved by allowing mdadm to know what was reshaped so far. This allows to reshape arrays that are not reshaped yet,
> without update from mdmon.
There certainly are some complexities with reshaping a container with 2 RAID0
arrays in it. However the approach you are taking seems too complicated.
This is how I think the particular case of 2 RAID0 array would work. It
should generalise neatly to all other combinations.
1/ mdadm decides to proceeds with the reshape, updates the metadata (because
mdmon isn't running), converts the array to RAID4, starts mdmon and then
lets the reshape for the first array proceed.
2/ when the reshape completes, mdmon will notice and will call
imsm_progress_container_reshape which will update the metadata
for the second array so that reshape appears to be active.
3/ mdadm will convert the raid4 back to raid0 and so mdmon will exit.
4/ mdadm calls container_content and finds that the second array needs to
be reshaped. It converts the array to raid4 and starts mdmon.
Then they oversee the reshape of the second array
5/ when the reshape completes, mdadm converts the array back to RAID0 and
mdmon exits.
All done.
This should avoid almost all special-casing.
NeilBrown
>
> BR
> Adam
>
> ---
>
> Adam Kwolek (6):
> FIX: sync_completed == 0 causes reshape cancellation in metadata
> FIX: mdadm hangs during reshape
> FIX: mdadm throws coredump on exit in error case
> FIX: reshape raid0 on second array
> FIX: continue raid0 reshape
> imsm: Update metadata for second array
>
>
> Grow.c | 95 +++++++++++++++++++++++++++++++++++++++++++++++++++------
> monitor.c | 4 ++
> super-intel.c | 35 +++++++++++++++++++--
> 3 files changed, 120 insertions(+), 14 deletions(-)
>
next prev parent reply other threads:[~2011-01-17 1:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 14:50 [PATCH 0/6] OLCE raid5/0 (all arrays in container) Adam Kwolek
2011-01-13 14:50 ` [PATCH 1/6] imsm: Update metadata for second array Adam Kwolek
2011-01-13 14:50 ` [PATCH 2/6] FIX: continue raid0 reshape Adam Kwolek
2011-01-13 14:50 ` [PATCH 3/6] FIX: reshape raid0 on second array Adam Kwolek
2011-01-13 14:50 ` [PATCH 4/6] FIX: mdadm throws coredump on exit in error case Adam Kwolek
2011-01-17 1:33 ` NeilBrown
2011-01-13 14:50 ` [PATCH 5/6] FIX: mdadm hangs during reshape Adam Kwolek
2011-01-17 1:37 ` NeilBrown
2011-01-17 9:43 ` Kwolek, Adam
2011-01-13 14:50 ` [PATCH 6/6] FIX: sync_completed == 0 causes reshape cancellation in metadata Adam Kwolek
2011-01-17 1:38 ` NeilBrown
2011-01-17 1:31 ` NeilBrown [this message]
2011-01-17 11:52 ` [PATCH 0/6] OLCE raid5/0 (all arrays in container) Kwolek, Adam
2011-01-19 20:41 ` 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=20110117123107.58d1024e@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).