linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: "Patrick J. LoPresti" <lopresti@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Resize RAID-0?
Date: Fri, 12 Mar 2010 11:36:52 +0000	[thread overview]
Message-ID: <73e903671003120336m36718a31m1c4ce760c42dbc75@mail.gmail.com> (raw)
In-Reply-To: <23986fd91003111939w102813c6r8d1b51a387784a71@mail.gmail.com>

On Fri, Mar 12, 2010 at 3:39 AM, Patrick J. LoPresti <lopresti@gmail.com> wrote:
> From reading the documentation and source code, I gather "mdadm
> --grow" is not supported for RAID-0 devices.
>
> In my application, I am using md RAID-0 to stripe among several
> (identical) hardware RAID-0 chassis.  I would like to extend my setup
> by adding another chassis, but apparently, I cannot (?).
>
> The next time I build a system like this, is there any way to get what
> I want using Linux?  That is, striping among devices, no parity, but
> with the ability to grow in the future?

I agree with others on the list - I believe that LVM will perform well
as a flexible stripe wrangler on top of mdadm arrays. For instance
some LVM striping over mdadm parity-based stuff underneath.

Do you want to add a whole new stripe device, so changing the
coarse-scale layout, or grow the underlying data containers?

I had a problem related to growing underlying containers which was
solved on the list a few weeks ago. I had two largish RAID6 arrays and
an mdadm stripe-set over those. I added some disks to both RAID6
subarrays and wanted to expand the stripe-array to use the space
gained. Here's a copy of the thread, "raid0 not growable?":
http://www.issociate.de/board/post/501375/raid0_not_growable?.html

But perhaps you wanted to do something like add a 3rd stripe to a
two-stripe array? (I myself don't know if that's possible or not.)

As you are running striped, I assume that the data is either
perishable or backed up. I'd suggest you look into moving to LVM. (LVM
has its quirks - so look before you leap, perhaps :) ) I suggest you
play a little with LVM in a virtual-machine; In the gas-lit and
magical world of open-source RAID management, there's nothing like
direct experience to tell you what's possible and what doesn't work.
The tools and the power are out there, but you have to do a little
hunting in the forest.

Best of luck!

-- Kristleifur
--
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

  parent reply	other threads:[~2010-03-12 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  3:39 Resize RAID-0? Patrick J. LoPresti
2010-03-12  5:17 ` Michael Evans
2010-03-12 10:40 ` John Robinson
2010-03-12 11:53   ` Neil Brown
2010-03-12 11:36 ` Kristleifur Daðason [this message]
2010-03-12 17:03   ` Patrick J. LoPresti
2010-03-13  0:09     ` Patrick J. LoPresti
2010-03-13  0:50       ` Neil Brown

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=73e903671003120336m36718a31m1c4ce760c42dbc75@mail.gmail.com \
    --to=kristleifur@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lopresti@gmail.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).