From: Simon Matthews <simon.d.matthews@gmail.com>
To: linux-raid@vger.kernel.org
Subject: Adding disks with raid to existing raid system.
Date: Sun, 14 Mar 2010 22:23:46 -0800 [thread overview]
Message-ID: <40b437201003142323g7b0f4e48wb9d58b963f12e988@mail.gmail.com> (raw)
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
next reply other threads:[~2010-03-15 6:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 6:23 Simon Matthews [this message]
2010-03-16 1:36 ` Adding disks with raid to existing raid system Michael Evans
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=40b437201003142323g7b0f4e48wb9d58b963f12e988@mail.gmail.com \
--to=simon.d.matthews@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).