From: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>
To: David Brown <david.brown@hesbynett.no>
Cc: Reindl Harald <h.reindl@thelounge.net>,
Jeff Allison <jeff.allison@allygray.2y.net>,
Adam Goryachev <mailinglists@websitemanagers.com.au>,
linux-raid@vger.kernel.org
Subject: Re: proactive disk replacement
Date: Tue, 21 Mar 2017 14:26:10 +0100 [thread overview]
Message-ID: <CAJH6TXih4wv10WDGOA2PT-b8FSetx06D237HS_cpT4+Ap0d0dg@mail.gmail.com> (raw)
In-Reply-To: <58D1244E.3040204@hesbynett.no>
2017-03-21 14:02 GMT+01:00 David Brown <david.brown@hesbynett.no>:
> Note that to cause failure in non-degraded RAID5 (or degraded RAID6),
> your two URE's need to be on the same stripe in order to cause data
> loss. The chances of getting an URE somewhere on the disk are roughly
> proportional to the size of the disk - but the chance of getting an URE
> on the same stripe as another URE on another disk are basically
> independent of the disk size, and it is extraordinarily small.
Little bit OT:
is this the same even for HW RAID Controllers like LSI Megaraid
or they tend to fail the rebuild in case of multiple URE even in
different stripes?
> No, you cannot. Your conclusion here is based on several totally
> incorrect assumptions:
>
> 1. You think that RAID5/RAID6 recovery is more stressful, because the
> parity is "all over the place". This is wrong.
>
> 2. You think that random IO has higher chance of getting an URE than
> linear IO. This is wrong.
Totally agree.
> 3. You think that getting an URE on one disk, then getting an URE on a
> second disk, counts as a double failure that will break an single-parity
> redundancy (RAID5, RAID1, RAID6 in degraded mode). This is wrong - it
> is only a problem if the two UREs are in the same stripe, which is quite
> literally a one in a million chance.
I'm not sure about this.
The posted paper is talking about "standard" raid made with hw raid controllers
and I'm not sure if they are able to finish a rebuild in case of double URE even
if coming from different stripes.
I think they fail the whole rebuild.
next prev parent reply other threads:[~2017-03-21 13:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 12:47 proactive disk replacement Jeff Allison
2017-03-20 13:25 ` Reindl Harald
2017-03-20 14:59 ` Adam Goryachev
2017-03-20 15:04 ` Reindl Harald
2017-03-20 15:23 ` Adam Goryachev
2017-03-20 16:19 ` Wols Lists
2017-03-21 2:33 ` Jeff Allison
2017-03-21 9:54 ` Reindl Harald
2017-03-21 10:54 ` Adam Goryachev
2017-03-21 11:03 ` Reindl Harald
2017-03-21 11:34 ` Andreas Klauer
2017-03-21 12:03 ` Reindl Harald
2017-03-21 12:41 ` Andreas Klauer
2017-03-22 4:16 ` NeilBrown
2017-03-21 11:56 ` Adam Goryachev
2017-03-21 12:10 ` Reindl Harald
2017-03-21 13:13 ` David Brown
2017-03-21 13:24 ` Reindl Harald
2017-03-21 14:15 ` David Brown
2017-03-21 15:25 ` Wols Lists
2017-03-21 15:41 ` David Brown
2017-03-21 16:49 ` Phil Turmel
2017-03-22 13:53 ` Gandalf Corvotempesta
2017-03-22 14:12 ` David Brown
2017-03-22 14:32 ` Phil Turmel
2017-03-21 11:55 ` Gandalf Corvotempesta
2017-03-21 13:02 ` David Brown
2017-03-21 13:26 ` Gandalf Corvotempesta [this message]
2017-03-21 14:26 ` David Brown
2017-03-21 15:31 ` Wols Lists
2017-03-21 17:00 ` Phil Turmel
2017-03-21 15:29 ` Wols Lists
2017-03-21 16:55 ` Phil Turmel
2017-03-22 14:51 ` John Stoffel
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=CAJH6TXih4wv10WDGOA2PT-b8FSetx06D237HS_cpT4+Ap0d0dg@mail.gmail.com \
--to=gandalf.corvotempesta@gmail.com \
--cc=david.brown@hesbynett.no \
--cc=h.reindl@thelounge.net \
--cc=jeff.allison@allygray.2y.net \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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).