From: Steve Cousins <steve.cousins@maine.edu>
To: Leon Avery <leon@eatworms.swmed.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: raidhotadd works, mdadm --add doesn't
Date: Mon, 11 Sep 2006 13:37:28 -0400 [thread overview]
Message-ID: <45059ED8.9030206@maine.edu> (raw)
In-Reply-To: <7.0.1.0.0.20060910150522.0360c060@eatworms.swmed.edu>
Leon Avery wrote:
> I've been using RAID for a long time, but have been using the old
> raidtools. Having just discovered mdadm, I want to switch, but I'm
> having trouble. I'm trying to figure out how to use mdadm to replace a
> failed disk. Here is my /proc/mdstat:
>
> Personalities : [linear] [raid1]
> read_ahead 1024 sectors
> md5 : active linear md3[1] md4[0]
> 1024504832 blocks 64k rounding
>
> md4 : active raid1 hdf5[0] hdh5[1]
> 731808832 blocks [2/2] [UU]
>
> md3 : active raid1 hde5[0] hdg5[1]
> 292696128 blocks [2/2] [UU]
>
> md2 : active raid1 hda5[0] hdc5[1]
> 48339456 blocks [2/2] [UU]
>
> md0 : active raid1 hda3[0] hdc3[1]
> 9765376 blocks [2/2] [UU]
>
> unused devices: <none>
>
> The relevant parts are md0 and md2. Physical disk hda failed, which
> left md0 and md2 running in degraded mode. Having an old spare used
> disk sitting on the shelf, I plugged it in, repartitioned it, and said
>
> mdadm --add /dev/md0 /dev/hda3
I think the thing to do is to list the md device before the --add :
mdadm /dev/md0 --add /dev/hda3
I use the -a form and do:
mdadm /dev/md0 -a /dev/hda3
Steve
next prev parent reply other threads:[~2006-09-11 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 20:30 raidhotadd works, mdadm --add doesn't Leon Avery
2006-09-11 17:37 ` Steve Cousins [this message]
2006-09-14 22:30 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2006-09-10 20:40 Leon Avery
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=45059ED8.9030206@maine.edu \
--to=steve.cousins@maine.edu \
--cc=leon@eatworms.swmed.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.