From: David Liontooth <liontooth@cogweb.net>
To: Guy <bugzilla@watkins-home.com>
Cc: 'Mario 'BitKoenig' Holbe' <Mario.Holbe@TU-Ilmenau.DE>,
linux-raid@vger.kernel.org
Subject: Re: RAID 16?
Date: Thu, 02 Feb 2006 16:59:20 -0800 [thread overview]
Message-ID: <43E2AAE8.7000507@cogweb.net> (raw)
In-Reply-To: <200602030020.k130KGq13372@www.watkins-home.com>
I appreciate all the expert feedback on this. We'll be able to make a
well-informed decision on how to proceed.
Best,
Dave
Guy wrote:
>He can loose 1 disk from any 2 RAID1 arrays. And then 2 disks from the
>other 2 RAID1 arrays. A total of 6 of 8 disks can fail if chosen correctly.
>
>I would go with an 8 disk RAID6, which would give the space of 6 disks and
>support any 2 disks failing. Or a 7 disk RAID6 with 1 spare, but I think
>that is over kill.
>
>Guy
>
>} -----Original Message-----
>} From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
>} owner@vger.kernel.org] On Behalf Of Mario 'BitKoenig' Holbe
>} Sent: Thursday, February 02, 2006 1:42 PM
>} To: linux-raid@vger.kernel.org
>} Subject: Re: RAID 16?
>}
>} Matthias Urlichs <smurf@smurf.noris.de> wrote:
>} > Hi, David Liontooth wrote:
>} >> * define 4 pairs of RAID 1 with an 8-port 3ware 9500S card * the OS
>} will
>} > Hmm. You'd have eight disks, five(!) may fail at any time, giving you
>}
>} Four, isn't it?
>} RAID6 covers the failure of 2 of the underlying RAID1s, which, in turn,
>} means failures of 2 disks each, so four.
>} Sometimes even 5, yes - given the right ones fail.
>}
>}
>} regards
>} Mario
>} --
>} We are the Bore. Resistance is futile. You will be bored.
>}
>} -
>} 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
>
>-
>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
>
>
next prev parent reply other threads:[~2006-02-03 0:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 5:59 RAID 16? David Liontooth
2006-02-02 6:03 ` Neil Brown
2006-02-02 8:34 ` Gordon Henderson
2006-02-02 16:17 ` Matthias Urlichs
2006-02-02 16:28 ` Mattias Wadenstein
2006-02-02 16:54 ` Gordon Henderson
2006-02-02 20:24 ` Matthias Urlichs
2006-02-02 21:18 ` J. Ryan Earl
2006-02-02 21:29 ` Andy Smith
2006-02-02 22:38 ` Konstantin Olchanski
2006-02-03 2:31 ` Ross Vandegrift
2006-02-03 2:54 ` Bill Davidsen
2006-02-02 18:42 ` Mario 'BitKoenig' Holbe
2006-02-02 20:34 ` Matthias Urlichs
2006-02-03 0:20 ` Guy
2006-02-03 0:59 ` David Liontooth [this message]
2006-02-02 16:44 ` Mr. James W. Laferriere
2006-02-03 9:08 ` Lars Marowsky-Bree
2006-02-03 2:32 ` Bill Davidsen
2006-02-05 23:42 ` Hard drive lifetime: wear from spinning up or rebooting vs running David Liontooth
2006-02-06 3:57 ` Konstantin Olchanski
2006-02-06 5:25 ` Patrik Jonsson
2006-02-06 4:35 ` Richard Scobie
2006-02-06 10:09 ` Mattias Wadenstein
2006-02-06 16:45 ` David Liontooth
2006-02-06 17:12 ` Francois Barre
2006-02-07 8:44 ` Hans Kristian Rosbach
2006-02-07 19:18 ` Neil Bortnak
2006-02-06 19:22 ` Brad Dameron
2006-02-06 21:15 ` Dan Stromberg
2009-09-20 19:44 ` RAID 16? Matthias Urlichs
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=43E2AAE8.7000507@cogweb.net \
--to=liontooth@cogweb.net \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--cc=bugzilla@watkins-home.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;
as well as URLs for NNTP newsgroup(s).