All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: cvb@kruemel.org
Cc: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>,
	linux RAID <linux-raid@vger.kernel.org>,
	linux-raid-owner@vger.kernel.org
Subject: Re: Is it possible to grow a (far) RAID 10?
Date: Wed, 26 Nov 2014 08:19:15 +1100	[thread overview]
Message-ID: <20141126081915.58d7fa71@notabene.brown> (raw)
In-Reply-To: <81fe7d20d731393c86a6ca557d71adaa@kruemel.org>

[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]

On Tue, 25 Nov 2014 12:01:58 +0100 cvb@kruemel.org wrote:

> Hi
> 
> Am 2014-11-25 10:25, schrieb Carsten Aulbert:
> > Without much thinking, I would simply follow the wiki page, mark a
> > device as failed, remove it, repartition it, add it again, and wait
> > for sync to complete. Repeat for all 4 devices and finally --grow with
> > mdadm (followed by xfs resizing) - and of course, all online, while
> > machine is in flight.
> 
> That is exactoy what I did with my RAID 10 a bit more than a year ago. 
> It basically worked, but there was one caveat... some part (the 
> ---grow?) which required a certain kernel version for which I had booted 
> a live CD back then...
> 
> The thing is, I can't exactly remember what the caveat was. And as I'm 
> about to grow the RAID again (having replaced all hard drives already), 
> I have been looking for the related mails in the archive of this list, 
> but I can't seem to find them...
> 
> So I guess we'll have to hope that Neil replies again.

I recommend creating some loop-back block devices and experimenting.

But I'm fairly sure that "far" RAID10 arrays cannot be reshaped at all.

NeilBrown

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]

  reply	other threads:[~2014-11-25 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  9:25 Is it possible to grow a (far) RAID 10? Carsten Aulbert
2014-11-25 11:01 ` cvb
2014-11-25 21:19   ` NeilBrown [this message]
2014-11-26  7:32     ` cvb

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=20141126081915.58d7fa71@notabene.brown \
    --to=neilb@suse.de \
    --cc=Carsten.Aulbert@aei.mpg.de \
    --cc=cvb@kruemel.org \
    --cc=linux-raid-owner@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.