From: NeilBrown <neilb@suse.de>
To: starlight.2012q4@binnacle.cx
Cc: linux-raid@vger.kernel.org
Subject: Re: question: no-bitmap RAID1 with off-site drive
Date: Tue, 13 Nov 2012 07:31:19 +1100 [thread overview]
Message-ID: <20121113073119.27f1a1db@notabene.brown> (raw)
In-Reply-To: <6.2.5.6.2.20121112131017.05df8b18@binnacle.cx>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Mon, 12 Nov 2012 13:11:50 -0500 starlight.2012q4@binnacle.cx wrote:
> Probably this is more elegant:
>
> mdadm --create --level=1 --raid-devices=2 --spare-devices=1 /dev/sdd /dev/sde missing
That is fairly meaningless ... I'm not sure it even works.
While it makes sense for raid devices to be missing, it doesn't make sense
for spares to be missing. Spares are just just any devices in the array
which aren't active. If they are missing, then they aren't spare.
NeilBrown
>
> At 12:26 PM 11/12/2012 -0500, starlight.2012q4@binnacle.cx wrote:
> >After some pondering, think I've figure it out.
> >
> >Best way to go is to set it up with
> >
> > --create --level=1 --raid-devices=2
> >
> >for the initial pair of drives, then
> >
> > --fail --remove
> >
> >the rotate-out drive, then
> >
> > --add
> >
> >the alternate drive. Now there will be
> >three drive slots with one "removed" and two
> >"active".
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-11-12 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 21:40 question: no-bitmap RAID1 with off-site drive starlight.2012q4
2012-11-11 22:14 ` starlight.2012q4
2012-11-12 3:40 ` Adam Goryachev
2012-11-12 14:55 ` starlight.2012q4
2012-11-12 17:56 ` Drew
[not found] ` <CACJz6Qt93zm47+576HSWBv+GGcNKKmz0G7+soAqPSMeBk2KFCg @mail.gmail.com>
2012-11-12 18:05 ` starlight.2012q4
2012-11-12 17:26 ` starlight.2012q4
2012-11-12 18:11 ` starlight.2012q4
2012-11-12 20:31 ` NeilBrown [this message]
2012-11-12 20:40 ` starlight.2012q4
2012-11-19 0:11 ` starlight.2012q4
2012-11-27 2:31 ` NeilBrown
2012-11-27 3:31 ` starlight.2012q4
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=20121113073119.27f1a1db@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=starlight.2012q4@binnacle.cx \
/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