linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Dirk Jagdmann <jagdmann@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: split raid1 into to arrays
Date: Tue, 27 Mar 2007 11:57:12 -0400	[thread overview]
Message-ID: <46093ED8.8020201@tmr.com> (raw)
In-Reply-To: <5d0f60990703261954l2bb8c225ocbc3cf66e868723a@mail.gmail.com>

Dirk Jagdmann wrote:
> Hello experts,
>
> I have a raid1 array with two drives working. It /dev/md0 built from
> /dev/hda and /dev/hdb. Now I'd like to split it into two array with
> one drive each (and then later add spares to my two arrays again). I
> know that I can remove one drive from the array with: mdadm /dev/md0
> -f /dev/hdb -r /dev/hdb , however I'm not sure what the superblock of
> /dev/hdb now contains and how I could use the contents of /dev/hdb as
> the starting point for my new /dev/md1 array? I did not find anything
> in the manpage of mdadm which would provide me an automatic split.
>
> So what are your advises?
>
The fast way (not redundant):
  You can mark hdb as failed, then remove it. Then you can create a new 
array using hdb and a missing device.

The safe way:
  get your additional drives, call then hdc and hdd just for discussion.
 add hdc to the existing array and let it rebuild, then mark hdb as 
failed and remove. Create a new array from hdb and hdd.

I'm sure someone will tell me if I left out a step.

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


  reply	other threads:[~2007-03-27 15:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27  2:54 split raid1 into to arrays Dirk Jagdmann
2007-03-27 15:57 ` Bill Davidsen [this message]
2007-03-29 10:01   ` Dirk Jagdmann

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=46093ED8.8020201@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jagdmann@gmail.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).