linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@keldix.com>
To: NeilBrown <neilb@suse.de>
Cc: "Keld Jørn Simonsen" <keld@keldix.com>,
	"Roberto Spadim" <roberto@spadim.com.br>,
	"Mathias Burén" <mathias.buren@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: expand raid10
Date: Wed, 13 Apr 2011 14:34:14 +0200	[thread overview]
Message-ID: <20110413123413.GA10377@www2.open-std.org> (raw)
In-Reply-To: <20110413211715.286d9203@notabene.brown>

On Wed, Apr 13, 2011 at 09:17:15PM +1000, NeilBrown wrote:
> On Wed, 13 Apr 2011 13:10:16 +0200 Keld Jørn Simonsen <keld@keldix.com> wrote:
> 
> > On Wed, Apr 13, 2011 at 07:47:26AM -0300, Roberto Spadim wrote:
> > > raid10 with other layout i could expand?
> > 
> > My understanding is that you currently cannot expand raid10.
> > but there are things in the works. Expansion of raid10,far
> > was not on the list from neil, raid10,near was. But it should be fairly
> > easy to expand raid10,far. You can just treat one of the copies as your
> > refence data, and copy that data to the other raid0-like parts of the
> > array.  I wonder if Neil thinks he could leave that as an exersize for
> > me to implement... I would like  to be able to combine it with a
> > reformat to a more robust layout of raid10,far that in some cases can survive more
> > than one disk failure.
> > 
> 
> I'm very happy for anyone to offer to implement anything.
> 
> I will of course require the code to be of reasonable quality before I accept
> it, but I'm also happy to give helpful review comments and guidance.
> 
> So don't wait for permission, if you want to try implementing something, just
> do it.
> 
> Equally if there is something that I particularly want done I won't wait for
> ever for someone else who says they are working on it.  But RAID10 reshape is
> a long way from the top of my list.

Hi Neil!

Yes, that is how I understand your policy on contributions.

Do you by RAID10 reshaping also mean RAID10 expansion?
In my eyes this is quite important, and something that I have wanted for
a long time. I think it is a quite common task for many Linux MD users.

best regards
keld
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-04-13 12:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  4:28 expand raid10 Roberto Spadim
2011-04-13  7:15 ` Mathias Burén
2011-04-13 10:47   ` Roberto Spadim
2011-04-13 11:10     ` Keld Jørn Simonsen
2011-04-13 11:17       ` NeilBrown
2011-04-13 12:34         ` Keld Jørn Simonsen [this message]
2011-04-13 23:28           ` NeilBrown
2011-04-13 12:34         ` David Brown
2011-04-13 23:36           ` NeilBrown
2011-04-14  8:16             ` David Brown
2011-04-15 16:52             ` Keld Jørn Simonsen
2011-04-18  0:46               ` 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=20110413123413.GA10377@www2.open-std.org \
    --to=keld@keldix.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.com \
    --cc=neilb@suse.de \
    --cc=roberto@spadim.com.br \
    /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).