linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristleifur Daðason" <kristleifur@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: raid0 not growable?
Date: Wed, 23 Dec 2009 23:28:37 +0000	[thread overview]
Message-ID: <73e903670912231528u6d3cd2ekd0fa4ade06adbcf5@mail.gmail.com> (raw)
In-Reply-To: <20091224094557.1ae96a0d@notabene>

On Wed, Dec 23, 2009 at 10:45 PM, Neil Brown <neilb@suse.de> wrote:
> On Wed, 23 Dec 2009 13:52:54 +0000
> Kristleifur Daðason <kristleifur@gmail.com> wrote:
>
>> Hi,
>>
>> I'm running a raid0 array over a couple of raid6 arrays. I had planned
>> on growing the arrays in time, and now turns out to be the time.
>>
>> To my chagrin, searches indicate that raid0 isn't growable. Can anyone
>> confirm this before I wipe and reconfigure?
>
> That is correct, you cannot currently grow md/raid0.
>
> If the two raid6 arrays are exactly the same size, then you
> could grow the two raid6 arrays, create a new raid0 over them
> with the same block size and all your data will still be there.
> But if they are not the same size, that won't work.
>
> NeilBrown
>

Many thanks for the reply. (Re-cc'd to the linux-raid list. Hope that's OK.)

1.
The raid6 arrays are exactly alike. Do I just do a create a new raid0
with the right size, device count and chunk-size parameters? I trust
your advice, but I am also certain of my own foolishness. I can't
fully picture what happens to the data on the array -- Specifically,
I'm thinking about whether to use --assume-clean or not. The
documentation says not. I am guessing that a newly-created raid0
doesn't do any syncing/resyncing anyway - it just sets up the array
structure and metadata and I am left to my own devices to fill it with
data.

Current chunksize is 256 and metadata is 1.1. So it's just a "mdadm
--create /dev/md_bigraid0 --level=0 --raid-devices=2 --metadata=1.1
--chunksize=256 /dev/md_raid6a /dev/md_raid6b", right?

2.
I have a JFS filesystem on the big raid0. Once I have the bigger raid0
built, I assume that I would first do a read-only fsck.jfs, which will
succeed if I did everything correctly. Then I do a remount with the
"resize" option to JFS to finally grow the JFS filesystem.

--

Sincere thanks. I hope I shall be able to contribute something
meaningful to mdadm when the company is richer and my time is freer :)
In the meantime, is there any preferred way of donating to mdadm or
sponsoring it?

-- 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:[~2009-12-23 23:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 13:52 raid0 not growable? Kristleifur Daðason
     [not found] ` <20091224094557.1ae96a0d@notabene>
2009-12-23 23:28   ` Kristleifur Daðason [this message]
2009-12-23 23:54     ` Neil Brown
2009-12-30 15:25       ` Kristleifur Daðason
2009-12-30 17:55         ` Kristleifur Daðason
2009-12-30  6:26 ` Billy Crook

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=73e903670912231528u6d3cd2ekd0fa4ade06adbcf5@mail.gmail.com \
    --to=kristleifur@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).