From: Frank Wittig <fw@weisshuhn.de>
To: John McMonagle <johnm@advocap.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Convert raid5 to raid1?
Date: Thu, 10 Mar 2005 23:34:14 +0100 [thread overview]
Message-ID: <4230CB66.8030705@weisshuhn.de> (raw)
In-Reply-To: <4230BE56.6090905@advocap.org>
John McMonagle wrote:
> Just wonder what happens to the md sequence when I remove the original
> raid arrays?
> When I'm done will I have md0,md1 and md2 or md2,md3 and md4?
they will have the name you entered when you created the array.
after removing one array from the system all arrays will still have
their original device-number after reboot.
greetings,
frank
next prev parent reply other threads:[~2005-03-10 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 21:38 Convert raid5 to raid1? John McMonagle
2005-03-10 22:34 ` Frank Wittig [this message]
2005-03-10 23:04 ` Brad Campbell
2005-03-10 23:13 ` Guy
2005-03-11 0:02 ` John McMonagle
2005-03-11 3:09 ` Guy
2005-03-11 8:58 ` David Greaves
2005-03-11 0:11 ` Paul Clements
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=4230CB66.8030705@weisshuhn.de \
--to=fw@weisshuhn.de \
--cc=johnm@advocap.org \
--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).