public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Unable to expand ext4 partition
Date: Sat, 5 Feb 2022 23:04:32 +0000	[thread overview]
Message-ID: <77828216-e307-7564-31bc-4ce8c7f07a4e@youngman.org.uk> (raw)
In-Reply-To: <MvAxMdj--3-2@jroy.ca>

On 05/02/2022 22:16, Julien Roy wrote:
> I didn't - I typically use the Gentoo and Arch wiki when I need 
> information, but will keep that in mind.
> I noticed, on that page, that there's a big bold warning about using 
> post-2019 WD Red drives. Sadly, that's exactly what I am doing, my array 
> is 4xWD60EFAX. I don't know whether that's the cause of the problem. It 
> does say on the wiki that these drives can't be added to existing 
> arrays, so it would make sense. Oh well, lesson learned.

  Ouch. EFAX drives are the new SMR version it seems. You might have 
been lucky, it might have added okay.

The problem with these drives, basically, is you cannot stream data to 
them. They'll accept so much, fill up their CMR buffers, and then stall 
while they do an internal re-organisation. And by the time they start 
responding again, the OS thinks the drive has failed ...

I've just bought a Toshiba N300 8TB for £165 as my backup drive. As far 
as I know that's an okay drive for raid - I haven't heard any bad 
stories about SMR being sneaked in ... I've basically split it in 2, 3TB 
as a spare partition for my raid, and 5TB as backup for my 6TB (3x3) 
raid array.

Look at creating a raid-10 from your WDs, or if you create a new raid-5 
array from scratch using --assume-clean then format it, you're probably 
okay. Replacing SMRs with CMRs will probably work fine so if one of your 
WDs fail, you should be okay replacing it, so long as it's not another 
SMR :-) (If you do a scrub, expects loads of parity errors first time 
:-) but you will probably get away with it if you're careful.

Cheers,
Wol


  reply	other threads:[~2022-02-05 23:04 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 [this message]
2022-02-06  0:37           ` Julien Roy
2022-02-06  0:47             ` Mark Knecht
2022-02-06  8:12               ` Wols Lists

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=77828216-e307-7564-31bc-4ce8c7f07a4e@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