From: Phil Turmel <philip@turmel.org>
To: dag@newtech.fi, Mikael Abrahamsson <swmike@swm.pp.se>
Cc: yuji_touya@yokogawa-digital.com, linux-raid@vger.kernel.org
Subject: Re: Help raid10 recovery from 2 disks removed
Date: Fri, 25 Oct 2013 08:21:09 -0400 [thread overview]
Message-ID: <526A6235.2020801@turmel.org> (raw)
In-Reply-To: <2614300.keHkAfZ48K@eseries.newtech.fi>
Good morning Dag,
On 10/25/2013 03:27 AM, Dag Nygren wrote:
> Just enabling scterc (which is disabled by default and will be
> after a power down of the drive), setting the timeout
> and then running a repair on the array
> fixed it for me as md was smart enough to try to rewrite the
> sector(s) that had failed and with scterc the drive would then reallocate
> the failed sector.
> I thought I had this done, but a syntax error in the script had
> prevented it from working.. :-( )
>
> The working script I ran for this was:
> =============================
> # Set up RAID drive timeouts
> for x in b c d e
> do
> smartctl -l scterc,70,70 /dev/sd$x
> echo 180 >/sys/block/sd$x/device/timeout
> done
> ==============================
You shouldn't do both. You only need the long driver timeout if the
hard disk doesn't support scterc. Long timeouts are bad for application
software, as you can get very long system pauses while waiting for a
sector recovery. But the long timeout is the only option if you have
non-scterc drives.
Some time ago I posted a similar script that checked the result code
from smartctl. It only resets the driver timeout if smartctl couldn't
set scterc.
HTH,
Phil
next prev parent reply other threads:[~2013-10-25 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 5:10 Help raid10 recovery from 2 disks removed yuji_touya
2013-10-24 8:54 ` Mikael Abrahamsson
2013-10-24 10:14 ` yuji_touya
2013-10-24 12:16 ` Phil Turmel
2013-10-25 10:47 ` yuji_touya
2013-10-25 12:07 ` Mikael Abrahamsson
2013-10-25 12:09 ` Phil Turmel
2013-10-24 12:44 ` Mikael Abrahamsson
2013-10-25 7:27 ` Dag Nygren
2013-10-25 8:24 ` Mikael Abrahamsson
2013-10-25 8:34 ` Dag Nygren
2013-10-25 10:08 ` yuji_touya
2013-10-25 12:21 ` Phil Turmel [this message]
2013-10-25 16:05 ` Dag Nygren
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=526A6235.2020801@turmel.org \
--to=philip@turmel.org \
--cc=dag@newtech.fi \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
--cc=yuji_touya@yokogawa-digital.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox