From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 or raid6 and the maximum size
Date: Thu, 22 Sep 2005 15:52:08 +0200 [thread overview]
Message-ID: <dgucu8$66q$1@sea.gmane.org> (raw)
In-Reply-To: 4332AD95.1080904@bppiac.hu
Farkas Levente <lfarkas@bppiac.hu> wrote:
> - 7 x 300GB in raid5 and one 300GB spare or
> - 8 x 300GB in raid6?
> it seems the same to me since both case we can get two disk faild and
No, it's everything but the same. raid5 always gives you survival of exactly
one simultaneous disk failure. If two of your disks fail simultaneously
in a raid5, you're lost. A spare disk gets used not before any disk
failed. Then it needs time to get synched, where you have no redundancy
at all. After that your raid5 is able to survive another disk failure.
regards
Mario
--
As a rule, the more bizarre a thing is, the less mysterious it proves to be.
-- Sherlock Holmes by Arthur Conan Doyle
next prev parent reply other threads:[~2005-09-22 13:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-22 13:11 raid5 or raid6 and the maximum size Farkas Levente
2005-09-22 13:52 ` Mario 'BitKoenig' Holbe [this message]
2005-09-22 16:28 ` berk walker
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='dgucu8$66q$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.de \
--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).