linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Peter Rabbitson <rabbit@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID0 to RAID5 upgrade
Date: Fri, 02 Mar 2007 15:31:35 -0500	[thread overview]
Message-ID: <45E889A7.5000408@tmr.com> (raw)
In-Reply-To: <20070301233905.GA13126@rabbit.us>

Peter Rabbitson wrote:
> On Thu, Mar 01, 2007 at 06:12:32PM -0500, Bill Davidsen wrote:
>   
>> I have three drives, with some various partitions, currently set up like 
>> this.
>>
>>  drive0    drive1    drive2
>>
>>   hdb1      hdi1      hdk1
>>   \_________RAID1________/
>>
>>   hdb2      hdi2      hdk2
>>  unused     \___RAID0____/
>>   200GB       100GB x 2
>>
>>             hdi3      hdk3
>>             \___unused___/
>>                100GB x 2
>>
>> What I want to have is 3 x 200 = 400GB RAID5.
>>
>> I would like to avoid copying 200GB of data to another machine and back 
>>     
>
> Can't you do the following:
>
> * copy the data from raid0 to hdb2 ( raid0 <= hdb2 you can even do a dd)
> * degrade raid1 to only contain drive0
> * since you have all your data on drive0, wipe drive1 and drive2 clean, 
> create a degraded raid5
> * copy stuff from drive0 to the new array (enw fs as well I presume)
> * resync the raid5 with drive0

The RAID1 is "most critical" data, and would never voluntarily be 
degraded. And since I only want to combine hd[ij][23] I would have no 
reason to do that. Other than that, it seems possible, assuming that 
mdadm will actually create the degraded RAID5 array with enough room for 
the data.

I'm testing that now.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      reply	other threads:[~2007-03-02 20:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-01 23:12 RAID0 to RAID5 upgrade Bill Davidsen
2007-03-01 23:39 ` Peter Rabbitson
2007-03-02 20:31   ` Bill Davidsen [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=45E889A7.5000408@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rabbit@rabbit.us \
    /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).