From: Neil Brown <neilb@suse.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Reshaping raid0/10
Date: Sat, 24 Feb 2007 07:17:12 +1100 [thread overview]
Message-ID: <17887.19400.179239.281711@notabene.brown> (raw)
In-Reply-To: message from Jan Engelhardt on Friday February 23
On Friday February 23, jengelh@linux01.gwdg.de wrote:
>
> On Feb 22 2007 06:59, Neil Brown wrote:
> >On Wednesday February 21, jengelh@linux01.gwdg.de wrote:
> >>
> >> are there any plans to support reshaping
> >> on raid0 and raid10?
> >>
> >
> >No concrete plans. It largely depends on time and motivation.
> >I expect that the various flavours of raid5/raid6 reshape will come
> >first.
> >Then probably converting raid0->raid5.
> >
> >I really haven't given any thought to how you might reshape a
> >raid10...
>
> It should not be any different from raid0/raid5 reshaping, should it?
Depends on what level you look at.
If I wanted to reshape a raid0, I would just morph it into a raid4
with a missing parity drive, then use the raid5 code to restripe it.
Then morph it back to regular raid0.
With raid10 I cannot do that. I would need to do the restriping
inside the raid10 module. But raid10 doesn't have a stripe-cache like
raid5 does, and the stripe cache is a very integral part of the
restripe process.
So there would be a substantial amount of design and coding to effect
a raid10 reshape - at least as much as the work to produce the initial
raid5 reshape and probably more.
So conceptually it might be very similar, but at the code level, it is
likely to be very different.
NeilBrown
next prev parent reply other threads:[~2007-02-23 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 16:28 Reshaping raid0/10 Jan Engelhardt
2007-02-21 19:59 ` Neil Brown
2007-02-22 6:09 ` dean gaudet
2007-02-23 12:59 ` Jan Engelhardt
2007-02-23 20:17 ` Neil Brown [this message]
2007-03-10 20:21 ` H. Peter Anvin
2007-03-10 21:19 ` Jan Engelhardt
2007-03-11 22:36 ` Neil Brown
2007-05-29 4:51 ` H. Peter Anvin
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=17887.19400.179239.281711@notabene.brown \
--to=neilb@suse.de \
--cc=jengelh@linux01.gwdg.de \
--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