linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Hardy <mhardy@h3c.com>
To: Robert Heinzmann <Robert.Heinzmann@gmx.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Migrating from SINGLE DISK to RAID1
Date: Tue, 01 Feb 2005 11:34:31 -0800	[thread overview]
Message-ID: <41FFD9C7.2090208@h3c.com> (raw)
In-Reply-To: <41FFD1F8.3010101@gmx.net>


Robert Heinzmann wrote:
> Hello,
> 
> can someone verify if the following statements are true ?
> 
> - It's not possible to simply  convert a existing partition with a 
> filesystem on it to a raid1 mirror set.

I believe you're right, but I'm not totally sure on this one. I'd take 
the second disk, create a new RAID1 with the first drive "missing" on 
the mdadm --create commandline, copy everything over to it, put grub on 
it, then test that it boots correctly by pulling the first drive out.

Only once the RAID1 is working (in degraded mode) add the original first 
drive back in, but booting off the RAID1, then add it to the RAID set to 
complete the pair. With that process, the question is somewhat moot, 
although I'm interested in the real answer too

> - Using a former disk of a raid1 array as a usual disk (not mounted as 
> degrated /dev/mdX, but instead mounted as /dev/sdX or /dev/hdX) is 
> successfull.
> 
> This is because the MD device layer reports the device size as size of 
> disk - superblock offset during the creation of a filesystem on the MD 
> device. Thus the used size of the disk, when mounting it as /dev/sdX 
> /dev/hdX, is some KB smaller than it could be, but no data is lost.

This matches my experience, although autodiscovery can get in your way, 
as you mention yourself

-Mike

  reply	other threads:[~2005-02-01 19:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01 19:01 Migrating from SINGLE DISK to RAID1 Robert Heinzmann
2005-02-01 19:34 ` Mike Hardy [this message]
2005-02-01 21:40   ` Robert Heinzmann
2005-02-01 23:52   ` Alvin Oga
2005-02-01 19:41 ` Paul Clements
2005-02-01 22:57 ` berk walker

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=41FFD9C7.2090208@h3c.com \
    --to=mhardy@h3c.com \
    --cc=Robert.Heinzmann@gmx.net \
    --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).