Linux RAID subsystem development
 help / color / mirror / Atom feed
From: starlight.2012q4@binnacle.cx
To: Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: question: no-bitmap RAID1 with off-site drive
Date: Mon, 12 Nov 2012 09:55:08 -0500	[thread overview]
Message-ID: <6.2.5.6.2.20121112095127.039df8b0@binnacle.cx> (raw)
In-Reply-To: <50A06F9F.3090600@websitemanagers.com.au>

At 02:40 PM 11/12/2012 +1100, Adam Goryachev wrote:
>5) madam --manage /dev/md2 --fail /dev/sdd (fail the disk you want to remove)
>6) mdadm --manage /dev/md2 --remove /dev/sdd (remove the disk from the array)

So this sequence will not harm the image
on the drive being roatated offsite?
Absolutely 100% for certain?  If there
is any chance of a problem I can
--stop the array before removing the
drive.  The volume is used for a Bacula
network backup that is often idle.

The third drive will never be on site
(think about the risk), but that just
means that the array will grow from
2->1 and then from 1->2 instead
of from 2->3 and 3->2.


  reply	other threads:[~2012-11-12 14:55 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 [this message]
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
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.20121112095127.039df8b0@binnacle.cx \
    --to=starlight.2012q4@binnacle.cx \
    --cc=linux-raid@vger.kernel.org \
    --cc=mailinglists@websitemanagers.com.au \
    /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