All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Edward Kuns <eddie.kuns@gmail.com>
Cc: Brad Campbell <lists2009@fnarfbargle.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Advice requested re: hard drive setup for RAID arrays
Date: Wed, 4 Nov 2015 15:09:25 -0500	[thread overview]
Message-ID: <563A65F5.4090301@turmel.org> (raw)
In-Reply-To: <CACsGCyQGChMLXfQ3G-DN+Y7mh9w7wFkmQ9274VFKBzSoOgaoUQ@mail.gmail.com>

Hi Edward,

On 11/04/2015 02:36 PM, Edward Kuns wrote:

> Is there a reasonable way of finding out if a shorter setting is 
> appropriate for any specific drive?

When I first learned all this (the hard way) with Seagate drives, 120
seconds was enough.  You'll find that in old archives, 2011-ish.  I
don't remember who, but someone had a drive that took longer and
suggested 180 seconds.

> Or would you say in general it's not worth the effort of trying to
> find out?

Not worth the effort.  It's a work-around for unsuitable devices until
such time as you can retire them.

> Would you expect this behavior to be any different for an SSD?

I'd expect an SSD's worst case error recovery to be much shorter --
there's no positioning to wait for, nor any mechanical effects that'll
make retrys meaningful.

Phil

      parent reply	other threads:[~2015-11-04 20:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 12:02 Advice requested re: hard drive setup for RAID arrays o1bigtenor
2015-11-04 13:13 ` Phil Turmel
2015-11-04 14:30   ` o1bigtenor
2015-11-04 15:05     ` Phil Turmel
     [not found]       ` <CAPpdf5_-3TOiCKq_dDTYGPcJMeEDMRD+xTAjkm-enmCnZPdtzg@mail.gmail.com>
2015-11-04 16:43         ` Phil Turmel
2015-11-04 17:27           ` Rudy Zijlstra
2015-11-05  6:02     ` Brad Campbell
2015-11-04 19:36   ` Edward Kuns
2015-11-04 19:42     ` Wols Lists
2015-11-04 20:09     ` Phil Turmel [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=563A65F5.4090301@turmel.org \
    --to=philip@turmel.org \
    --cc=eddie.kuns@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.