From: Chris Mason <chris.mason@oracle.com>
To: Chris Ball <cjb@laptop.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Building a RAID post-mkfs?
Date: Mon, 26 Oct 2009 18:35:00 +0900 [thread overview]
Message-ID: <20091026093500.GE5564@think> (raw)
In-Reply-To: <m3skdjusvx.fsf@pullcord.laptop.org>
On Fri, Oct 16, 2009 at 01:54:10PM -0400, Chris Ball wrote:
> Hi,
>
> I installed btrfs to one disk using the Fedora 12 installer; it
> doesn't allow any configuration of the mkfs command by the user,
> so it wasn't possible to mkfs with more than one disk.
>
> I'd like to add a second disk, with either RAID0 or RAID1 between
> the two -- the equivalent of "mkfs.btrfs -m raid0/1 -d raid0/1
> /dev/sda /dev/sdb". Is it possible to create this non-destructively
> now? If not, should it be? What would the implementation look like?
It's not very complex, you can take a look at how we upgrade from
single spindle dup to RAID1 for metadata when a second disk is added.
Basically once we have a block group with the new type we're able to
force new allocations to the new raid level. btrfs-vol -b does the
rest.
-chris
prev parent reply other threads:[~2009-10-26 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 17:54 Building a RAID post-mkfs? Chris Ball
2009-10-26 9:35 ` Chris Mason [this message]
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=20091026093500.GE5564@think \
--to=chris.mason@oracle.com \
--cc=cjb@laptop.org \
--cc=linux-btrfs@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