From: Mitchell Laks <mlaks@verizon.net>
To: linux-raid@vger.kernel.org
Subject: Re: How to move a singleton raid1 drive from raid1 /dev/md2 to /dev/md1
Date: Fri, 08 Apr 2005 00:29:39 -0400 [thread overview]
Message-ID: <200504080029.39899.mlaks@verizon.net> (raw)
In-Reply-To: <16980.51185.391624.438300@cse.unsw.edu.au>
Thanks you Neil!!
i am running debian sarge with 1.9 and kernel 2.6.8
I followed your instructions
mdadm -S /dev/md2 # shutdown md2 and release hde1
mdadm /dev/md1 -a /dev/hde1 # add hde1 as a spare in md1
mdadm -G -n2 /dev/md1 # grow md1 to have two devices.
and now
wustl@A1:~$ cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 hdb1[0] hdg1[1]
244195904 blocks [2/2] [UU]
md1 : active raid1 hde1[1] hdc1[0]
244195904 blocks [2/2] [UU]
Yay!!!
Thank you very much.
Mitchell
prev parent reply other threads:[~2005-04-08 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 5:25 How to move a singleton raid1 drive from raid1 /dev/md2 to /dev/md1 Mitchell Laks
2005-04-07 5:41 ` Neil Brown
2005-04-08 4:29 ` Mitchell Laks [this message]
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=200504080029.39899.mlaks@verizon.net \
--to=mlaks@verizon.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).