Linux RAID subsystem development
 help / color / mirror / Atom feed
From: starlight.2012q4@binnacle.cx
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: question: no-bitmap RAID1 with off-site drive
Date: Mon, 12 Nov 2012 15:40:36 -0500	[thread overview]
Message-ID: <6.2.5.6.2.20121112153741.039df248@binnacle.cx> (raw)
In-Reply-To: <20121113073119.27f1a1db@notabene.brown>

Thank you!  Still working to wrap my brain
around 'md'.  Will stick with the first
approach.

Amusingly I performed it by accident,
was confused and frustrated by result,
then eventually realized it was ideal.




At 07:31 AM 11/13/2012 +1100, NeilBrown wrote:
>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
>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".
>> 
>> --
>
>


  reply	other threads:[~2012-11-12 20:40 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
2012-11-12 20:40       ` starlight.2012q4 [this message]
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=6.2.5.6.2.20121112153741.039df248@binnacle.cx \
    --to=starlight.2012q4@binnacle.cx \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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