From: Phillip Susi <psusi@cfl.rr.com>
To: Berkey B Walker <berk@panix.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Growing a single disk into a 2 disk raid0
Date: Fri, 28 Jan 2011 13:19:16 -0500 [thread overview]
Message-ID: <4D4308A4.5000800@cfl.rr.com> (raw)
In-Reply-To: <4D4302B6.2090208@panix.com>
On 1/28/2011 12:53 PM, Berkey B Walker wrote:
> Because 1) I'm old, and 2) I don't trust documentation, I do it the
> slow, easy way. I use the blank disk and make a RAID missing a disk. I
> then copy the data to the RAIDed disk. If everything is OK, zero out
> the old data disk and add it to the raid (filling the "missing"). I do
> it this way any time I want to make raid of a disk full of data, to
> any level of raid.
That works for raid1, but as I said, mdadm will not let you create a
single disk raid0.
next prev parent reply other threads:[~2011-01-28 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 17:17 Growing a single disk into a 2 disk raid0 Phillip Susi
2011-01-28 17:53 ` Berkey B Walker
2011-01-28 18:14 ` John Robinson
2011-01-28 18:29 ` Phillip Susi
2011-01-29 1:38 ` Hank Barta
2011-01-28 18:19 ` Phillip Susi [this message]
2011-01-29 9:10 ` NeilBrown
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=4D4308A4.5000800@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=berk@panix.com \
--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).