From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] which linux RAID setup to choose?
Date: Sun, 3 May 2020 15:52:57 -0700 [thread overview]
Message-ID: <CAK2H+ecrEHG9dRf8ucVNt-4JYH8muR651-p1YQMqrWVEOV_xDQ@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_kv_qc7kQ8VwaCmNmszScbn-OKm1o=CFt5_kzZROHZMMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
On Sun, May 3, 2020 at 1:16 PM Rich Freeman <rich0@gentoo.org> wrote:
>
> On Sun, May 3, 2020 at 2:29 PM Mark Knecht <markknecht@gmail.com> wrote:
> >
> > I've used the WD Reds and WD Golds (no not sold) and never had any
problem.
> >
>
> Up until a few weeks ago I would have advised the same, but WD was
> just caught shipping unadvertised SMR in WD Red disks. This is going
> to at the very least impact your performance if you do a lot of
> writes, and it can be incompatible with rebuilds in particular with
> some RAID implementations. Seagate and Toshiba have also been quietly
> using it but not in their NAS-labeled drives and not as extensively in
> general.
I read somewhere that they knew they'd been caught and were coming clean.
As I'm not buying anything at this time I didn't pay too much attention.
This link is at least similar to what I read earlier. Possibly it's of
interest.
https://www.extremetech.com/computing/309730-western-digital-comes-clean-shares-which-hard-drives-use-smr
Another case of unbridled capitalism and consumers being hurt.
Cheers,
Mark
[-- Attachment #2: Type: text/html, Size: 1608 bytes --]
next prev parent reply other threads:[~2020-05-03 22:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 5:44 [gentoo-user] which linux RAID setup to choose? Caveman Al Toraboran
2020-05-03 7:53 ` hitachi303
2020-05-03 9:23 ` Wols Lists
2020-05-03 17:55 ` Caveman Al Toraboran
2020-05-03 18:04 ` Dale
2020-05-03 18:29 ` Mark Knecht
2020-05-03 20:16 ` Rich Freeman
2020-05-03 22:52 ` Mark Knecht [this message]
2020-05-03 23:23 ` Rich Freeman
2020-05-03 21:22 ` antlists
2020-05-03 9:14 ` Wols Lists
2020-05-03 9:21 ` Caveman Al Toraboran
2020-05-03 14:27 ` Jack
2020-05-03 21:46 ` Caveman Al Toraboran
2020-05-03 22:50 ` hitachi303
2020-05-04 0:29 ` Caveman Al Toraboran
2020-05-04 7:50 ` hitachi303
2020-05-04 0:46 ` Rich Freeman
2020-05-04 7:50 ` hitachi303
2020-05-04 8:18 ` William Kenworthy
2020-05-03 23:19 ` antlists
2020-05-04 1:33 ` Caveman Al Toraboran
2020-05-03 20:07 ` Rich Freeman
2020-05-03 21:32 ` antlists
2020-05-03 22:34 ` Rich Freeman
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=CAK2H+ecrEHG9dRf8ucVNt-4JYH8muR651-p1YQMqrWVEOV_xDQ@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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