All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reindl Harald <h.reindl@thelounge.net>
To: Phillip Susi <phill@thesusis.net>
Cc: Wols Lists <antlists@youngman.org.uk>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: raid10 redundancy
Date: Tue, 18 May 2021 21:02:28 +0200	[thread overview]
Message-ID: <ae729a44-b3fb-48ef-617a-6ba9efaffec7@thelounge.net> (raw)
In-Reply-To: <87wnrvdg4n.fsf@vps.thesusis.net>



Am 18.05.21 um 20:51 schrieb Phillip Susi:
> 
> Reindl Harald writes:
> 
>> it's common sense that additional load on drives which have the same
>> history makes a failure one one of them more likely
> 
> "It's common sense" = the logical fallacy of hand waving.  Show me
> statistical evidence.  I have had lightly loaded drives die in under 2
> years and heavily loaded ones last 10 years.  I have replaced failed
> drives in a raid and the other drives with essentially the same wear on
> them lasted for years without another failure.  There does not appear to
> be a strong correlation usage and drive failure.  Certainly not one that
> is so strong that you can claim with a straight face that after the
> first failure, a second one can be expected within X IOPS, and the IOPS
> needed to rebuild the array are a significant fraction of X

do what you want - others like to be better safe then sorry especially 
when there is no longer redundancy and you don't surive any error until 
the rebuild is finished

and yes i replaced last week a 365/24 for years running Seagate *desktop 
drive* in a RAID10 with 50k power up hours but that don't imply that you 
can expect that

  reply	other threads:[~2021-05-18 19:02 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  5:09 raid10 redundancy d tbsky
2021-05-06  7:48 ` Xiao Ni
2021-05-06  9:57   ` d tbsky
2021-05-06 12:38     ` Reindl Harald
2021-05-07  1:28       ` d tbsky
2021-05-08 13:47         ` keld
2021-05-09  0:52           ` Phillip Susi
2021-05-12 17:22             ` David T-G
2021-05-12 17:26               ` Reindl Harald
2021-05-12 17:39                 ` David T-G
2021-05-13 15:38               ` Andy Smith
2021-05-13 15:46               ` Phillip Susi
2021-05-13 15:59                 ` Andy Smith
2021-05-14 14:28                   ` Phillip Susi
2021-05-14 14:37                     ` Andy Smith
2021-05-17  2:07                       ` Brad Campbell
2021-05-06 13:09     ` Phillip Susi
2021-05-07  1:47       ` d tbsky
     [not found]         ` <86A76859-3098-4AB8-9AE7-46FF54736B88@websitemanagers.com.au>
2021-05-07  3:05           ` d tbsky
2021-05-07  3:26         ` Reindl Harald
2021-05-07 14:53         ` Andy Smith
2021-05-08  1:54           ` d tbsky
2021-05-08  5:55             ` Andy Smith
2021-05-09  1:10         ` Phillip Susi
2021-05-07  1:26     ` d tbsky
2021-05-06 10:39 ` Peter Grandi
2021-05-07  1:37   ` d tbsky
     [not found] ` <AD8C004B-FE83-4ABD-B58A-1F7F8683CD1F@websitemanagers.com.au>
2021-05-07  1:12   ` d tbsky
2021-05-07  9:46     ` Wols Lists
2021-05-11  0:04       ` Phil Turmel
2021-05-12 17:27         ` David T-G
2021-05-12 18:20           ` Phil Turmel
2021-05-12 16:31 ` Roy Sigurd Karlsbakk
2021-05-13 15:38   ` Phillip Susi
2021-05-13 18:21     ` Phil Turmel
2021-05-14 14:30       ` Phillip Susi
2021-05-14 14:48         ` Roy Sigurd Karlsbakk
2021-05-17 20:50           ` Phillip Susi
2021-05-17 22:21             ` Wols Lists
2021-05-18  0:12               ` Phil Turmel
2021-05-18 16:05               ` Phillip Susi
2021-05-18 17:38                 ` Reindl Harald
2021-05-18 18:51                   ` Phillip Susi
2021-05-18 19:02                     ` Reindl Harald [this message]
2021-05-18 23:48                 ` antlists
2021-05-19  3:42                   ` Adam Goryachev
2021-05-19 13:02                     ` Phillip Susi
2021-05-19 21:19                       ` Reindl Harald
2021-05-20  1:32                       ` Adam Goryachev
     [not found]                         ` <CAAMCDeeOnraMDNCF6ZZqPAxUrih2gSse1wDYgOfd1LqY-Ffqxw@mail.gmail.com>
2021-05-20 15:08                           ` antlists

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=ae729a44-b3fb-48ef-617a-6ba9efaffec7@thelounge.net \
    --to=h.reindl@thelounge.net \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=phill@thesusis.net \
    --cc=roy@karlsbakk.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.