linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Weedy <weedy2887@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Thomas Fjellstrom <thomas@fjellstrom.ca>,
	Phil Turmel <philip@turmel.org>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Recent drive errors
Date: Fri, 22 May 2015 03:07:17 -0400	[thread overview]
Message-ID: <CAFE24U2WvC+tn9gYLKbgBHLg2QqOedvOmPD8PgHaCGp_+PYAxg@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1505210956210.9487@uplift.swm.pp.se>

On Thu, May 21, 2015 at 3:58 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Tue, 19 May 2015, Thomas Fjellstrom wrote:
>
>> How many UREs are considered "ok"? Tens, hundreds, thousands, tens of
>> thousands?
>
>
> I will replace any drive that have developed UNC sectors a few times, so I'd
> say "less than 10".
>
> +1 on the "set kernel timeout to more than 120 seconds". I have this in
> /etc/rc.local:
>
> for x in /sys/block/sd[a-z] ; do
>         echo 180  > $x/device/timeout
> done
>
> echo 4096 > /sys/block/md0/md/stripe_cache_size

#!/bin/sh

if [ -e /proc/sys/dev/raid/speed_limit_min ]; then
    echo $((1024*4)) > /proc/sys/dev/raid/speed_limit_min 2> /dev/null
    echo $((1024*24)) > /proc/sys/dev/raid/speed_limit_max 2> /dev/null
fi
if [ -e /dev/md0 -o -d /dev/md ]; then
    for md in /dev/md*; do
        echo $((1024*4)) > /sys/block/${md#/dev/}/md/stripe_cache_size
        blockdev --setra $((1024*4)) /dev/${md#/dev/}
    done
    for disk in /sys/block/sd*; do
        echo 45 > $disk/device/timeout
        smartctl -l scterc,70,70 /dev/${disk#/sys/block/}
    done
fi
for disk in /sys/block/sd*; do
    echo  cfq     > $disk/queue/scheduler
    echo  768    > $disk/queue/read_ahead_kb
    echo  256    > $disk/queue/nr_requests
    echo    8    2>/dev/null    > $disk/device/queue_depth
done

      parent reply	other threads:[~2015-05-22  7:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 11:08 Recent drive errors Thomas Fjellstrom
2015-05-19 12:34 ` Phil Turmel
2015-05-19 12:50   ` Thomas Fjellstrom
2015-05-19 13:23     ` Phil Turmel
2015-05-19 14:32       ` Thomas Fjellstrom
2015-05-19 14:51         ` Phil Turmel
2015-05-19 16:07           ` Thomas Fjellstrom
2015-05-20  5:38             ` Thomas Fjellstrom
2015-05-21  7:58     ` Mikael Abrahamsson
2015-05-21 12:45       ` Thomas Fjellstrom
2015-05-22 13:38         ` Mikael Abrahamsson
2015-05-22 14:19           ` Thomas Fjellstrom
2015-05-22  7:07       ` Weedy [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=CAFE24U2WvC+tn9gYLKbgBHLg2QqOedvOmPD8PgHaCGp_+PYAxg@mail.gmail.com \
    --to=weedy2887@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    --cc=swmike@swm.pp.se \
    --cc=thomas@fjellstrom.ca \
    /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;
as well as URLs for NNTP newsgroup(s).