Linux RAID subsystem development
 help / color / mirror / Atom feed
From: starlight.2012q4@binnacle.cx
To: Drew <drew.kay@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: question: no-bitmap RAID1 with off-site drive
Date: Mon, 12 Nov 2012 13:05:54 -0500	[thread overview]
Message-ID: <6.2.5.6.2.20121112130511.05dfe610@binnacle.cx> (raw)
In-Reply-To: <CACJz6Qt93zm47+576HSWBv+GGcNKKmz0G7+soAqPSMeBk2KFCg @mail.gmail.com>

Good point but not an issue here.

Have daily offsite cloud incremental backup
in the mix here (i.e. forth drive).

The array does nothing but receive
incremental Bacula archives once a day
in the early AM.  So there's no
moving target data loss potential.


At 09:56 AM 11/12/2012 -0800, Drew wrote:
>> 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.
>
>I'd argue your risk from a failing disk during
>resync is significantly greater then your risk
>of facility failure during the same window. Not
>sure what drives are pricing where you are but
>adding a forth into the rotation is cheap
>insurance. Two for the array, one syncing, one
>offsite.
>
>Some recent blogs (
>http://storagemojo.com/2010/02/27/does-raid-6-stops-working-in-2
>019/
>for example ) suggest that modern drives will
>encounter unrecoverable read errors approx every
>12TB read. That works out to approx every
>6-12 resyncs based on 1-2TB drives.
>
>
>-- 
>Drew
>--
>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


  parent reply	other threads:[~2012-11-12 18:05 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 [this message]
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.20121112130511.05dfe610@binnacle.cx \
    --to=starlight.2012q4@binnacle.cx \
    --cc=drew.kay@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox