All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Campbell <lists2009@fnarfbargle.com>
To: o1bigtenor <o1bigtenor@gmail.com>, Phil Turmel <philip@turmel.org>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Advice requested
Date: Wed, 04 Nov 2015 12:31:46 +0800	[thread overview]
Message-ID: <56398A32.1040503@fnarfbargle.com> (raw)
In-Reply-To: <CAPpdf5_0A0r9s5aCQOn3M9etUnw_2SLMVig3pH+4vfKZDh=8kQ@mail.gmail.com>

On 04/11/15 12:05, o1bigtenor wrote:
> On Tue, Nov 3, 2015 at 10:01 PM, o1bigtenor <o1bigtenor@gmail.com> wrote:
>>
>>
>>
>> On Tue, Nov 3, 2015 at 10:08 AM, Phil Turmel <philip@turmel.org> wrote:
>>> One caveat -- don't do this part until you've corrected your timeout mismatch
>>> problem, or any latent UREs will break your array again.
>>
>>
>>
>> Read through the references.
>>
>> How do I do what you suggest?

Here's how I do it. This script is run on every bootup.

It iterates through all the drives and uses smartctl to try and set erc 
timeouts. If that fails it assumes the drive does not support it and it 
sets the timeout value to 180 seconds.

#!/bin/bash
for i in /dev/sd? ; do
	if smartctl -l scterc,70,70 $i > /dev/null ; then
		echo -n $i " is good "
	else
		echo 180 > /sys/block/${i/\/dev\/}/device/timeout
		echo -n $i " is  bad "
	fi;
	smartctl -i $i | egrep "(Device Model|Product:)"
	blockdev --setra 1024 $i
done

I have a mix of 15k SAS drives, WD green & red and some left over bits 
and pieces. This ensures the timeouts all match the drives capability.

Regards,
Brad

  reply	other threads:[~2015-11-04  4:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31 11:55 Advice requested o1bigtenor
2015-11-01 20:55 ` Phil Turmel
     [not found]   ` <CAPpdf5_PUpR7GhBHUaQfWb8Q+7FZenxXgFqbaN3f3r0r6NQNDA@mail.gmail.com>
2015-11-02 15:41     ` Phil Turmel
     [not found]       ` <CAPpdf59MFX1oVwLC-bmQBaQp9K_9-+h0v64OGMnV1-k=eCzO0w@mail.gmail.com>
     [not found]         ` <5637BCE4.8000006@turmel.org>
2015-11-02 23:49           ` o1bigtenor
2015-11-03  0:11             ` Phil Turmel
2015-11-03  0:44               ` o1bigtenor
2015-11-03  0:57                 ` Phil Turmel
2015-11-03  1:02                   ` o1bigtenor
2015-11-03  1:55                     ` Phil Turmel
2015-11-03  4:03                       ` o1bigtenor
2015-11-03  4:09                         ` Phil Turmel
2015-11-03  4:28                           ` o1bigtenor
2015-11-03  4:47                             ` Phil Turmel
2015-11-03 12:45                               ` o1bigtenor
2015-11-03 13:09                                 ` Phil Turmel
2015-11-03 13:36                                   ` o1bigtenor
2015-11-03 15:49                                     ` Adam Goryachev
2015-11-03 16:08                                     ` Phil Turmel
     [not found]                                       ` <CAPpdf59o0kf1-mgB29AcgH2cpdwBrhazf3NeQUYNa6m9+c6C+A@mail.gmail.com>
2015-11-04  4:05                                         ` o1bigtenor
2015-11-04  4:31                                           ` Brad Campbell [this message]
2015-11-03 18:02       ` Phil Turmel
2015-11-03 19:06         ` o1bigtenor

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=56398A32.1040503@fnarfbargle.com \
    --to=lists2009@fnarfbargle.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=o1bigtenor@gmail.com \
    --cc=philip@turmel.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 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.