From: Vlad Dobrotescu <vlad@dobrotescu.ca>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 questions (mdadm 3.2.6/3.3.x)
Date: Sat, 12 Jul 2014 13:15:44 -0400 [thread overview]
Message-ID: <53C16D40.7040002@dobrotescu.ca> (raw)
In-Reply-To: <EAE4EA52-392A-4191-AA1B-B3B9BEFEBA60@colorremedies.com>
Chris Murphy <lists <at> colorremedies.com> writes:
>
> On Jul 12, 2014, at 7:30 AM, Vlad Dobrotescu <vlad <at> dobrotescu.ca>
> wrote:
> >
> > Since it seems you have a very healthy view of real-world RAID,
> > could you point out any significant issues when using a disk as
> > a degraded md RAID1 (not accidental, but on purpose)?
>
> Intentionally degraded raid1 seems oxymoronic to me. Like fat free
> ice cream. Uptime/data availability is the purpose of RAID, not
> backup. It sounds like a member drive is being used as a shelf or
> offsite backup, with periodic catch-up resyncing. If it's an n way
> mirror with 3 drives, two left connected, one off-site, then while
> technically degraded you could still lose one drive and have uptime
> and a backup. But I still think that's the wrong way to do it —
> this is probably more of a philosophical argument than a technical
> one.
>
> Chris Murphy
As mentioned in my original message, this would be a setup that can
accomodate "hot-replace" (without a full resync) before this feature
becomes available in mdadm 3.3.x ...
Vlad
--
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
prev parent reply other threads:[~2014-07-12 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 22:41 RAID6 questions (mdadm 3.2.6/3.3.x) Vlad Dobrotescu
2014-07-12 1:09 ` Chris Murphy
2014-07-12 1:20 ` NeilBrown
2014-07-12 3:21 ` Vlad Dobrotescu
2014-07-13 3:15 ` NeilBrown
2014-07-13 6:07 ` Vlad Dobrotescu
2014-07-12 12:29 ` Piergiorgio Sartor
2014-07-12 3:20 ` Vlad Dobrotescu
2014-07-12 3:46 ` Chris Murphy
2014-07-12 13:30 ` Vlad Dobrotescu
2014-07-12 14:46 ` Chris Murphy
2014-07-12 17:15 ` Vlad Dobrotescu [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=53C16D40.7040002@dobrotescu.ca \
--to=vlad@dobrotescu.ca \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.