linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: "Renaud (Ron) OLGIATI" <renaud@olgiati-in-paraguay.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Choosing a SATA HD for RAID1
Date: Sat, 29 Feb 2020 10:28:15 +0000	[thread overview]
Message-ID: <5E5A3CBF.4060706@youngman.org.uk> (raw)
In-Reply-To: <20200229071940.29a6320a@olgiati-in-paraguay.org>

On 29/02/20 10:19, Renaud (Ron) OLGIATI wrote:
> On Sat, 29 Feb 2020 09:18:29 +0000
> Wols Lists <antlists@youngman.org.uk> wrote:
> 
>> On 29/02/20 02:47, Hans Malissa wrote:
>>> I'm trying to select suitable SATA HD for RAID1 via mdadm. 
> 
> As an aside on this thread, should one aim to build RAID arrays from HDs of the same make and model, or on the contrary diversify HDs in the hope that disks of different makers and model are less likely to fail at the same time ?
>  
It's widely accepted that you should not buy all your raid disks at the
same time from the same manufacturer, precisely because they will
probably all suffer from similar defects.

Drives tend to fail quickly from defects, or wear out slowly from use.
Especially in a raid array where usage patterns are very similar, that
means you don't want similar drives with similar usage as they'll wear
out together.

Throw in the fact that rebuilding an array regularly stresses the other
drives to the point of failure ...

So no. Don't buy your drives in one hit. Either spread them out over
time, or mix models and manufacturers. With that said, a home user like
me is more likely to deliberately retire a drive than have it fail, so
from my point of view it's pretty irrelevant. And nowadays, with good
quality drives, that's also true for many companies - if an enterprise
drive comes with a five-year warranty and you expect to retire the drive
because it's become too small in five years time, well, the probability
that they'll all fail together is too small to worry about. The
probability that ONE drive will fail is tiny, let alone more ...

Cheers,
Wol

  parent reply	other threads:[~2020-02-29 10:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-29  2:47 Choosing a SATA HD for RAID1 Hans Malissa
2020-02-29  9:18 ` Wols Lists
     [not found]   ` <20200229071940.29a6320a@olgiati-in-paraguay.org>
2020-02-29 10:28     ` Wols Lists [this message]
2020-02-29 18:08   ` Hans Malissa
2020-03-01  0:33     ` 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=5E5A3CBF.4060706@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=renaud@olgiati-in-paraguay.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).