public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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 11:29:42 -0700	[thread overview]
Message-ID: <CAK2H+ecU7igf07vxWx8usutorX6=0muQMW=qP3Wn8sQPYQ1JFA@mail.gmail.com> (raw)
In-Reply-To: <b9d_3eoWjtJfTaNdA4fsbBTzboGj66ZLDY6JDm2IJy-qIHjlNcBWjHUmeVlRp3Eu8iUkNtopw2_aBMTw0VMTeFZz0uVsMMnYyiFgjh1ZH8g=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]

On Sun, May 3, 2020 at 10:56 AM Caveman Al Toraboran <
toraboracaveman@protonmail.com> wrote:
>
> On Sunday, May 3, 2020 1:23 PM, Wols Lists <antlists@youngman.org.uk>
wrote:
>
> > For anything above raid 1, MAKE SURE your drives support SCT/ERC. For
> > example, Seagate Barracudas are very popular desktop drives, but I guess
> > maybe HALF of the emails asking for help recovering an array on the raid
> > list involve them dying ...
> >
> > (I've got two :-( but my new system - when I get it running - has
> > ironwolves instead.)
>
> that's very scary.
>
> just to double check:  are those help emails about
> linux's software RAID?  or is it about hardware
> RAIDs?
>
> the reason i ask about software vs. hardware, is
> because of this wiki article [1] which seems to
> suggest that mdadm handles error recovery by
> waiting for up to 30 seconds (set in
> /sys/block/sd*/device/timeout) after which the
> device is reset.
>
> am i missing something?  to me it seems that [1]
> seems to suggest that linux software raid has a
> reliable way to handle the issue?  since i guess
> all disks support resetting well?
>
> [1] https://en.wikipedia.org/wiki/Error_recovery_control#Software_RAID
>

When doing Linux RAID, hardware or software, make sure you get a RAID aware
drive that supports TLER (Time Limited Error Recovery) or whatever the
vendor that makes your drive calls it. Typically this is set at about 7
seconds guaranteeing that no mater what's going on the drive will respond
to the upper layers (mdadm) to let it know it's alive. A non-RAID drive
with no TLER feature will respond when it's ready and typically if that's
longer than 30 seconds then the RAID subsystem kicks the drive and you have
to re-add it. While there's nothing 'technically' wrong with the storage
when the RAID rebuilds you eventually hit another on of these >30 second
waits and another drive gets kicked and you're dead.

I've used the WD Reds and WD Golds (no not sold) and never had any problem.

Build a RAID with a WD Green and you're in for trouble. ;-)))

HTH,
Mark

[-- Attachment #2: Type: text/html, Size: 2691 bytes --]

  parent reply	other threads:[~2020-05-03 18:30 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 [this message]
2020-05-03 20:16         ` Rich Freeman
2020-05-03 22:52           ` Mark Knecht
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+ecU7igf07vxWx8usutorX6=0muQMW=qP3Wn8sQPYQ1JFA@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