From: Phil Turmel <philip@turmel.org>
To: Roberto Nunnari <roberto.nunnari@supsi.ch>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: replacing drives
Date: Tue, 30 Apr 2013 11:11:32 -0400 [thread overview]
Message-ID: <517FDF24.9000807@turmel.org> (raw)
In-Reply-To: <517FD7BE.8040401@supsi.ch>
On 04/30/2013 10:39 AM, Roberto Nunnari wrote:
> Mikael Abrahamsson wrote:
>> On Tue, 30 Apr 2013, Roberto Nunnari wrote:
>>
>>> How do I increase that timeout?
>>
>> for x in /sys/block/sd[a-z] ; do echo 180 > $x/device/timeout ; done
>
> what the... these are SECONDS! What on earth could delay a sata attached
> disk read for 30 (now 180) seconds if not a disk failure? I OS hang?
> Sorry about that question, but I don't understand.. I have never seen
> such a problem.
The worst horror stories on this mailing list are directly attributable
to this problem. Usually after months or even years of apparently
trouble-free operation.
Consumer-grade drives intended for desktop usage are not
"out-of-the-box" compatible with RAID. Some of them are configurable
after each power-up to behave like an enterprise drive. The rest must
be accommodated with extended driver timeouts.
Search the list archives for "scterc", "timeout", and "URE" (or
combinations thereof).
Phil
next prev parent reply other threads:[~2013-04-30 15:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 14:27 replacing drives Roberto Nunnari
2013-04-26 15:36 ` Tregaron Bayly
2013-04-26 15:42 ` Keith Keller
2013-04-26 15:53 ` Robin Hill
2013-04-30 13:17 ` Roberto Nunnari
2013-04-30 13:20 ` Mikael Abrahamsson
2013-04-30 14:11 ` Roberto Nunnari
2013-04-30 14:22 ` Robin Hill
2013-04-30 14:40 ` Mikael Abrahamsson
2013-04-30 14:27 ` Roberto Nunnari
2013-04-30 14:39 ` Roberto Nunnari
2013-04-30 14:42 ` Mikael Abrahamsson
2013-04-30 15:10 ` Roberto Nunnari
2013-04-30 15:11 ` Phil Turmel [this message]
2013-04-30 15:39 ` Roberto Spadim
2013-05-01 1:55 ` Brad Campbell
2013-05-01 15:06 ` Roberto Nunnari
2013-05-01 18:14 ` Roberto Spadim
2013-05-02 17:49 ` Roy Sigurd Karlsbakk
2013-05-02 17:43 ` Roy Sigurd Karlsbakk
2013-04-30 13:45 ` Robin Hill
2013-04-30 14:05 ` Roberto Nunnari
2013-04-30 14:28 ` Roberto Nunnari
2013-04-30 15:19 ` Roberto Nunnari
2013-05-02 13:56 ` Roberto Nunnari
2013-05-02 14:54 ` Robin Hill
2013-05-02 15:00 ` Roberto Nunnari
2013-05-03 16:28 ` Roberto Nunnari
2013-05-06 11:30 ` Roberto Nunnari
2013-05-07 7:53 ` Robin Hill
2013-05-07 10:22 ` Roberto Nunnari
2013-05-08 14:19 ` Roberto Nunnari
2013-05-08 15:10 ` Robin Hill
2013-05-08 16:05 ` Roberto Nunnari
2013-05-08 17:01 ` Robin Hill
2013-05-08 17:20 ` Roberto Nunnari
2013-05-10 21:35 ` Roberto Nunnari
2013-04-26 22:20 ` Roberto Nunnari
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=517FDF24.9000807@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=roberto.nunnari@supsi.ch \
--cc=swmike@swm.pp.se \
/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.