From: antlists <antlists@youngman.org.uk>
To: John Stoffel <john@stoffel.org>, Ian Pilcher <arequipeno@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID types & chunks sizes for new NAS drives
Date: Tue, 23 Jun 2020 16:36:51 +0100 [thread overview]
Message-ID: <290bc100-6fb4-84bc-83ac-eed1be3d8cb6@youngman.org.uk> (raw)
In-Reply-To: <24305.24232.459249.386799@quad.stoffel.home>
On 23/06/2020 02:45, John Stoffel wrote:
> In any case, make sure you get NAS rated disks, either the newest WD
> RED+ (or is it Blue?) In any case, make sure to NOT get the SMR
> (Shingled Magnetic Recording) format drives. See previous threads in
> this group, as well as the arstechnica.com discussion about it all
> that they disk last month. Very informative.
I'd just avoid WD completely. They advertise REDs as raid-capable, and
they are (mostly) SMR and unfit for purpose. BLUEs are supposedly the
"desktop performance" drives, so sticking them in a raid is not advised
anyway. But you've only got to start hammering your BLUE performance
drive, and performance would be abysmal. If you are going for WD then
RED PRO is what you need.
At least Seagate don't advertise unsuitable drives - DON'T touch
Barracudas! They say Ironwolf or Ironwolf Pro for raid, both are fine to
the best of my knowledge.
And nobody seems to buy Toshiba but - I think it's the N300 - they do a
raid range as well.
Don't buy REDs or Barracudas or other known-problematic drives. They
will appear to work fine until there's a problem, at which point they
will bork the raid and lose your data. A good raid drive will tell the
raid it's failed and let the raid recover. These problem drives DON'T
tell the raid what's going on, and by the time the raid finds out it's
too late.
Cheers,
Wol
next prev parent reply other threads:[~2020-06-23 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 16:23 RAID types & chunks sizes for new NAS drives Ian Pilcher
2020-06-23 1:45 ` John Stoffel
2020-06-23 2:31 ` o1bigtenor
2020-06-23 17:01 ` John Stoffel
2020-06-24 22:13 ` o1bigtenor
2020-06-23 12:26 ` Nix
2020-06-23 18:50 ` John Stoffel
2020-06-23 15:36 ` antlists [this message]
2020-06-23 18:55 ` John Stoffel
2020-06-24 12:32 ` Phil Turmel
2020-06-24 14:49 ` John Stoffel
2020-06-24 18:41 ` Wols Lists
2020-06-23 20:27 ` Ian Pilcher
2020-06-23 21:30 ` John Stoffel
2020-06-23 23:16 ` Ian Pilcher
2020-06-24 0:34 ` 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=290bc100-6fb4-84bc-83ac-eed1be3d8cb6@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=arequipeno@gmail.com \
--cc=john@stoffel.org \
--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