linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Adam Goryachev <adam@websitemanagers.com.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Can't expand linear RAID on top of 2 x RAID1
Date: Fri, 22 Jun 2012 18:05:22 -0500	[thread overview]
Message-ID: <4FE4FA32.8010506@hardwarefreak.com> (raw)
In-Reply-To: <4FE44BDD.302@websitemanagers.com.au>

On 6/22/2012 5:41 AM, Adam Goryachev wrote:
> I have expanded my system over time, I started with 2 x 2TB drives in
> RAID1 (md2)
> 
> I then added 2 x 750GB drives, configured as RAID1 (md1)
> Then created a third raid (md3) as linear with the md2 + md1
> 
> Finally, I've upgraded the 2 x 750G to 2 x 1TB drives (one at a time).
> 
> I then did a mdadm --grow to expand the RAID1 from 750G to 1TB
> 
> The problem I am having is that I can't expand the linear (md3) array to
> grow the extra 250G of space.
> 
> Could anyone suggest how I might be able to get the extra 250G of space
> to become available?

If you think about this for a few minutes more, and re-read how md
--linear works, and thus how growing a linear array works, you'll surely
understand why you can't do what you're attempting to do.

As for seeing that extra 250GB, I don't have an answer.  Typically
linear arrays are used in lieu of growing constituent member arrays.
That's kinda the whole point of linear (concatenation).

You could try deleting the linear array and simply creating a new one.
But surely the changed offsets would wreak havoc on the filesystem
currently spanning this mess.

-- 
Stan

  reply	other threads:[~2012-06-22 23:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 10:41 Can't expand linear RAID on top of 2 x RAID1 Adam Goryachev
2012-06-22 23:05 ` Stan Hoeppner [this message]
2012-06-23  2:53   ` Adam Goryachev
2012-06-23 12:18     ` Stan Hoeppner
2012-06-24 14:17       ` Stan Hoeppner
2012-06-25  2:52     ` NeilBrown
2012-06-29  7:53       ` Adam Goryachev

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=4FE4FA32.8010506@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=adam@websitemanagers.com.au \
    --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;
as well as URLs for NNTP newsgroup(s).