From: antlists <antlists@youngman.org.uk>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Recommended filesystem for RAID 6
Date: Sun, 23 Aug 2020 00:50:35 +0100 [thread overview]
Message-ID: <cb519e5f-a603-8254-2c5b-0f983431aeb1@youngman.org.uk> (raw)
In-Reply-To: <CAJCQCtRkLmfQ9BHy1ymYU=LC95LA2b2-Pyf_Gm8X06cza1YUjw@mail.gmail.com>
On 22/08/2020 19:50, Chris Murphy wrote:
> How can you tell? From the spec, I can't find anything that indicates
> it. Let alone which of three varieties it is.
> https://www.seagate.com/www-content/product-content/barracuda-fam/barracuda-new/en-us/docs/100805918d.pdf
Simple.
Seagate now say that all the BarraCuda range are SMR. And this is a
BarraCuda, not a Barracuda. (What's the difference, you say? The capital C.)
I've been digging, and I think if you want an old-fashioned CMR desktop
drive you need the BarraCuda Pro or FireCuda. But at least - like the WD
Reds or Red Pluses, there is at least an official naming convention that
tells you what's what.
https://www.seagate.com/gb/en/internal-hard-drives/cmr-smr-list/
This is linked to on the wiki timeout problem page, as is the official
WD statement.
Cheers,
Wol
next prev parent reply other threads:[~2020-08-22 23:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 4:42 Recommended filesystem for RAID 6 George Rapp
2020-08-11 15:06 ` Roy Sigurd Karlsbakk
2020-08-11 19:19 ` Michael Fritscher
2020-08-11 19:45 ` Wols Lists
2020-08-22 1:31 ` David C. Rankin
2020-08-22 7:25 ` Peter Grandi
2020-08-22 9:38 ` Wols Lists
2020-08-22 19:21 ` Chris Murphy
2020-08-22 19:04 ` Chris Murphy
2020-08-22 18:50 ` Chris Murphy
2020-08-22 19:54 ` Kai Stian Olstad
2020-08-22 23:50 ` antlists [this message]
2020-08-12 14:07 ` Nix
2020-08-11 15:22 ` antlists
2020-08-11 16:23 ` Roman Mamedov
2020-08-11 18:57 ` Reindl Harald
2020-08-11 19:33 ` Roman Mamedov
2020-08-11 19:49 ` Rudy Zijlstra
2020-08-11 20:13 ` Roman Mamedov
2020-08-11 20:17 ` Reindl Harald
2020-08-11 20:12 ` Reindl Harald
2020-08-11 22:14 ` Roy Sigurd Karlsbakk
2020-08-12 14:16 ` Nix
2020-08-12 14:41 ` Roman Mamedov
2020-08-12 20:44 ` Peter Grandi
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=cb519e5f-a603-8254-2c5b-0f983431aeb1@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=lists@colorremedies.com \
/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.