From: Michael Evans <mjevans1983@gmail.com>
To: Simon Matthews <simon.d.matthews@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Adding disks with raid to existing raid system.
Date: Mon, 15 Mar 2010 17:36:04 -0800 [thread overview]
Message-ID: <4877c76c1003151836r56d03faeh50d8bfd1bb2925cf@mail.gmail.com> (raw)
In-Reply-To: <40b437201003142323g7b0f4e48wb9d58b963f12e988@mail.gmail.com>
On Sun, Mar 14, 2010 at 10:23 PM, Simon Matthews
<simon.d.matthews@gmail.com> wrote:
> I have just built a system and have it booting off a software raid
> partition. The raid sets use devices /dev/md0, /dev/hd1, /dev/md2,
> /dev/md3.
>
> I now need to transfer some additional disks to this system. These
> disks are presently in another system where they host a number of raid
> sets, currently also /dev/md0 - /dev/md4.
>
> I need to ensure that the data on the raid set that I am adding to the
> system is not lost. However, clearly, I can't have the raid sets on
> these disks come up as /dev/md0-md4. How do I ensure this and have
> these raid sets come up on /dev/md5 and higher?
>
> Simon
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Either use an mdadm.conf to specify the mapping of UUID to md device
(which will over-ride any auto-detected requests), or use the
home-host fallback. Obviously the administrator specifying how they'd
prefer mdadm to assemble the drives is preferable.
You will probably want to regenerate your initrd; if you are using
auto-assembly on root without an initrd, I highly suggest upgrading to
use an initrd/initramfs. You might find this one easy to customize
for your needs if your distribution lacks one or you dislike the one
it generates: http://sourceforge.net/projects/aeuio/
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-16 1:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 6:23 Adding disks with raid to existing raid system Simon Matthews
2010-03-16 1:36 ` Michael Evans [this message]
2010-03-16 3:53 ` Simon Matthews
2010-03-16 4:59 ` Michael Evans
2010-03-16 5:31 ` Simon Matthews
2010-03-21 0:30 ` Simon Matthews
2010-03-21 0:47 ` Michael Evans
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=4877c76c1003151836r56d03faeh50d8bfd1bb2925cf@mail.gmail.com \
--to=mjevans1983@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=simon.d.matthews@gmail.com \
/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).