From: Neil Brown <neilb@cse.unsw.edu.au>
To: BOIK MOON <mooasun@yahoo.com>
Cc: bluca@comedia.it, linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE - mdadm 0.8 - candidate for 1.0
Date: Thu, 11 Apr 2002 09:57:15 +1000 (EST) [thread overview]
Message-ID: <15540.53595.552654.565603@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from BOIK MOON on Wednesday April 10
On Wednesday April 10, mooasun@yahoo.com wrote:
>
> Neil,
>
> I tried with "mdadm -C /dev/md0 --level raid1 --raid-disks 2 /dev/hda1 --fail /dev/hdc1"
> to make a MD device with a faulty device. However, It did not work what I expected.
> I do not want to include /dev/hdc1 yet because it has the system image, but it tried to
> include it.
> Any suggestion?
Yes. If you don't want /dev/hdc1 to be included, don't include it.
If you say:
# mdadm -C /dev/md0 --level raid1 --raid-disks 2 /dev/hda1
It will say:
mdadm: You haven't given enough devices (real or missing) to create this array
The word "missing" is meant to be a hint, but I don't think it is
documented (I've just made a TODO note to fix that - thanks).
The command:
# mdadm -C /dev/md0 --level raid1 --raid-disks 2 /dev/hda1 missing
will create your array with /dev/hda1 in the first slot, and no device
in the second slot.
NeilBrown
prev parent reply other threads:[~2002-04-10 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15531.46606.314167.19186@notabene.cse.unsw.edu.au>
[not found] ` <Pine.GSO.4.21.0204032025070.9004-100000@gecko.roadtoad.net>
[not found] ` <15531.56527.518603.63636@notabene.cse.unsw.edu.au>
2002-04-07 12:56 ` ANNOUNCE - mdadm 0.8 - candidate for 1.0 Luca Berra
2002-04-10 1:05 ` Neil Brown
[not found] ` <20020410203945.99811.qmail@web10405.mail.yahoo.com>
2002-04-10 23:57 ` Neil Brown [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=15540.53595.552654.565603@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=bluca@comedia.it \
--cc=linux-raid@vger.kernel.org \
--cc=mooasun@yahoo.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).