All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Brad Campbell <lists2009@fnarfbargle.com>,
	Francisco Parada <advanceandconquer@gmail.com>
Cc: mdraid <linux-raid@vger.kernel.org>
Subject: Re: RAID6 - CPU At 100% Usage After Reassembly
Date: Tue, 11 Oct 2016 10:23:31 +0100	[thread overview]
Message-ID: <57FCAF93.9040305@youngman.org.uk> (raw)
In-Reply-To: <63380999-4291-97e9-41e4-363903e5c07b@fnarfbargle.com>

On 11/10/16 04:53, Brad Campbell wrote:
> On 07/10/16 19:23, Francisco Parada wrote:
> 
>> issue with the model drives that I'm using.  I've got WD 3TB Green
>> EZRX drives, which I recently found out via the RAID Wiki, that they
>> didn't have error correction (after I spent over a thousand dollars on
>> the drives in 3 years) ... Had I known better, I would have opted for
>> different models.
> 
> That's not entirely true. EZRX drives have just as much "error
> correction" as any other drive. What they don't have is the ability to
> rapidly terminate their error correction (WD call it Time Limited Error
> Recovery or TLER). Nothing wrong with that provided your OS storage
> stack timeouts are set appropriately, as without that the drives will
> take longer to process the error than the OS will wait and things get
> ugly resulting in drives kicked from arrays.
> 
> Sure, they're not the best drives for the job, and buying new I wouldn't
> recommend them; but disable periodic head parking and spindown, set the
> timeouts appropriately and they'll do the job until they need replacing.
> 
I've put your timeout fix script on the wiki :-)

It strikes me this would be a good addition too - I could probably
manage something of the sort, but do you or anyone have the code to
detect a green, and do that "disable parking and spindown"? It's a pain,
but having a script that deals with all known and common issues with
drives is probably a good thing.

I ought to go through that script and comment it heavily - I know the
experts will say "Why?" :-) but (although I may be a guru elsewhere)
this is an area I'm learning - hopefully fast - and comments are helpful
when reading code :-) They can always be deleted in production.

Cheers,
Wol


  reply	other threads:[~2016-10-11  9:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04  4:04 RAID6 - CPU At 100% Usage After Reassembly Francisco Parada
2016-09-04 14:38 ` Michael J. Shaver
     [not found]   ` <CAOW94uv4zSGs+6be3zhcQaGZdiAgg-s4ZHZ=mszcURo6pqJyqA@mail.gmail.com>
2016-09-04 22:48     ` Francisco Parada
2016-09-13 15:22       ` Francisco Parada
2016-09-13 17:43         ` Shaohua Li
2016-09-13 18:15           ` Francisco Parada
     [not found]             ` <CAOW94utVBcLz191ifzKkjn+nsSthPWDAQF8R-PabcS2uPareag@mail.gmail.com>
2016-09-26 14:29               ` Francisco Parada
2016-09-30 13:06                 ` Francisco Parada
2016-10-05 11:12                   ` Francisco Parada
2016-10-06 23:55                     ` Shaohua Li
2016-10-07 11:23                       ` Francisco Parada
2016-10-10 19:52                         ` Anthony Youngman
2016-10-11  3:53                         ` Brad Campbell
2016-10-11  9:23                           ` Wols Lists [this message]
2016-10-11 12:46                             ` Brad Campbell
  -- strict thread matches above, loose matches on Subject: below --
2016-09-04  2:56 Francisco Parada

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=57FCAF93.9040305@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=advanceandconquer@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.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.