From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>,
Wols Lists <antlists@youngman.org.uk>, Nix <nix@esperi.org.uk>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: New setup: partitions or raw devices
Date: Sat, 2 Dec 2017 14:14:07 +0100 [thread overview]
Message-ID: <6066a947-2a4e-d8d5-239d-dccb80e39ac0@gmail.com> (raw)
In-Reply-To: <1d3830e8-9e5e-681c-d556-1b8b6524dda2@thelounge.net>
Il 02/12/2017 00:44, Reindl Harald ha scritto:
> a RAID10 can survive two faile disks while a RAID5 is for sure dead
Absolutely not.
This is a common misconception.
RAID-10 can survive two failed disks IF AND ONLY IF these disks are on
different mirrors.
I had multiple (more than 4) RAID-10s totally lost due to double failure
in the same mirror.
Each disk in a mirror will get the same write pattern, thus, you'll risk
a double failure for any
firmware bugs or similiar. With SSDs this risk is higher, because you
wear out both members
in the same way at the same time.
If the controller kicks out two adiacent disks, you'll loose everything
(this is happened to me: fully synced RAID10: disk0 was kicked out by
the controller, RAID
survived and after a couple of minutes, disk0 was automatically
reactivated and started a rebuild.
during the rebuild, disk1 was kicked out. RAID lost: disk0 out-of-sync
and disk1 kicked out)
RAID-6 is *much* more safe than RAID-1/RAID-10 as it can survive ANY TWO
disks failure,
you will loose data on the third failure.
next prev parent reply other threads:[~2017-12-02 13:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 16:22 New setup: partitions or raw devices Gandalf Corvotempesta
2017-11-29 16:44 ` Reindl Harald
2017-11-29 16:52 ` Phil Turmel
2017-11-29 17:42 ` Gandalf Corvotempesta
2017-11-29 17:49 ` Phil Turmel
[not found] ` <CAJH6TXjFoUOCySnq2ErjTT9rb10XSc2saY=Q3RDheT7thOOFPg@mail.gmail.com>
[not found] ` <CAJH6TXhK5XgY-1v49oHcRXBugDMZ6QagKSa-deCA-Q7tPPLRyA@mail.gmail.com>
[not found] ` <CAJH6TXgbfgg_dk9oasVExn=RPVZqQDKN2AWAmPi1U2=PiACAHA@mail.gmail.com>
2017-11-29 19:54 ` Fwd: " Gandalf Corvotempesta
2017-11-29 22:10 ` Chris Murphy
2017-11-29 22:14 ` Gandalf Corvotempesta
2017-11-29 22:27 ` Chris Murphy
2017-11-29 22:14 ` Chris Murphy
2017-11-29 17:38 ` Gandalf Corvotempesta
2017-11-29 18:28 ` Reindl Harald
2017-11-29 19:51 ` Gandalf Corvotempesta
2017-11-29 20:02 ` Reindl Harald
2017-11-29 22:02 ` Gandalf Corvotempesta
2017-11-29 22:10 ` Reindl Harald
2017-11-29 22:25 ` Gandalf Corvotempesta
2017-11-29 22:34 ` Reindl Harald
2017-12-01 16:18 ` Nix
2017-12-02 13:01 ` Gandalf Corvotempesta
2017-11-29 22:20 ` Wol's lists
2017-11-29 22:27 ` Reindl Harald
2017-12-01 16:19 ` Nix
2017-12-01 16:27 ` Reindl Harald
2017-12-01 17:18 ` Wols Lists
2017-12-01 22:22 ` Nix
2017-12-01 23:44 ` Reindl Harald
2017-12-02 13:14 ` Gandalf Corvotempesta [this message]
2017-12-02 13:56 ` Reindl Harald
2017-12-02 17:12 ` Phil Turmel
2017-12-02 18:39 ` Reindl Harald
2017-12-02 13:19 ` Nix
2017-12-02 14:01 ` Reindl Harald
2017-12-02 20:35 ` Nix
2017-12-02 21:41 ` Reindl Harald
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=6066a947-2a4e-d8d5-239d-dccb80e39ac0@gmail.com \
--to=gandalf.corvotempesta@gmail.com \
--cc=antlists@youngman.org.uk \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--cc=nix@esperi.org.uk \
/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