From: Robin Hill <robin@robinhill.me.uk>
To: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: 3 disk RAID1?
Date: Mon, 8 Mar 2010 20:58:03 +0000 [thread overview]
Message-ID: <20100308205803.GA31731@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <5bdc1c8b1003081239l32c5653fs8347179e23c0a287@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
On Mon Mar 08, 2010 at 12:39:26PM -0800, Mark Knecht wrote:
> Hi all,
> I'm still very much on a steep learning curve about what I can do
> with Linux software RAID. In another thread this weekend a couple of
> responders discussed among themselves 3-disk RAID1 solutions that can
> survive if 2 disks die. I don't understand what that means. Can
> someone point me at a quick explanation? Is that really possible?
>
> In general I'm using a few Wikipedia pages and gravitate toward the
> diagrams as much as anything.
>
> http://en.wikipedia.org/wiki/RAID
> http://en.wikipedia.org/wiki/RAID1#RAID_1
>
> RAID0 - striping, speed not reliability (2 disk minimum)
> RAID1 - duplicate data, no other protection (2 disk minimum)
>
> How do I build RAID1 using three drives? Just duplicate the data 3
> times? If drives start going bad how do I determine which one or two
> are failing? (fsck? SMART?) With 3 drives 1 fail seems relatively
> straightforward to figure out, but 2?
>
A 3-disk RAID1 is just 3 duplicate copies, yes. And RAID only protects
against hardware failures, so you know which disk has failed because it
gets kicked out of the array as faulty. This is the same regardless of
how many mirrored copies you have (md will detect a write failure to a
drive and mark it as faulty - read errors will cause the failed block to
get rewritten).
As for how to create it - it's just the same process as for a 2-disk
RAID1 but specifying 3 drives (assuming you're using Linux md software
RAID - if not, please specify what you're intending to use). The manual
page for mdadm should give you everything you need - do ask if there's
anything you want clarifying though.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-08 20:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 20:39 3 disk RAID1? Mark Knecht
2010-03-08 20:58 ` Robin Hill [this message]
2010-03-08 21:04 ` Mark Knecht
2010-03-08 22:11 ` Michael Evans
2010-03-08 22:18 ` Kristleifur Daðason
2010-03-09 1:19 ` Mark Knecht
2010-03-09 1:26 ` Leslie Rhorer
2010-03-09 3:17 ` Michael Evans
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=20100308205803.GA31731@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--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;
as well as URLs for NNTP newsgroup(s).