From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Unable to expand ext4 partition
Date: Sun, 6 Feb 2022 08:12:45 +0000 [thread overview]
Message-ID: <d1e5b39b-6f56-d861-82e5-b78bc03aa66f@youngman.org.uk> (raw)
In-Reply-To: <CAK2H+edSGYCrP8-fApqLjW4KUC-FS9Oxj0O-kQJQORvfbACc8Q@mail.gmail.com>
On 06/02/2022 00:47, Mark Knecht wrote:
> If it's a WD Red Plus on the label then it's CMR and good. If it's WD
> Red without the "Plus" then it's SMR and WD has said don't use them
> for this purpose. It's not impossible to run the WD Red in a RAID, but
> they tend to fail when resilvering. If it resilvers correctly then it
> will probably be OK at least in the short term but you should consider
> getting a couple of Red Plus and having them on hand if the plain WD
> Red goes bad.
Avoid WD ...
I've got two 4TB Seagate Ironwolves and a 8TB Toshiba N300.
I've also got two 3TB Barracudas, but they're quite old and I didn't
know they were a bad choice for raid. From what I can make out, Seagate
has now split the Barracuda line in two, and you have the BarraCuda (all
SMR) and FireCuda (all CMR) aimed at the desktop niche. So you might
well be okay with a FireCuda but neither Seagate nor us raid guys would
recommend it.
Cheers,
Wol
prev parent reply other threads:[~2022-02-06 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 17:43 [gentoo-user] Unable to expand ext4 partition Julien Roy
2022-02-05 19:09 ` Wol
2022-02-05 19:37 ` Julien Roy
2022-02-05 22:02 ` Wols Lists
2022-02-05 22:16 ` Julien Roy
2022-02-05 23:04 ` Wol
2022-02-06 0:37 ` Julien Roy
2022-02-06 0:47 ` Mark Knecht
2022-02-06 8:12 ` Wols Lists [this message]
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=d1e5b39b-6f56-d861-82e5-b78bc03aa66f@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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