From: Phil Turmel <philip@turmel.org>
To: Kyle Logue <teque5@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Wierd: Degrading while recovering raid5
Date: Tue, 10 Feb 2015 21:14:21 -0500 [thread overview]
Message-ID: <54DABAFD.6070101@turmel.org> (raw)
In-Reply-To: <CAP7a4USu+650JJh9yX-WUU6eyxOGowa5r72W8JABCJpLnO=gtg@mail.gmail.com>
Hi Kyle,
{ Convention on kernel.org lists is reply-to-all, trim replies, and
either bottom post or interleave }
On 02/10/2015 04:50 PM, Kyle Logue wrote:
> Phil:
>
> Thanks for your detailed response. That link does seem to describe my
> problem and I do understand that desktop grade drives are sub-optimal.
> It was many years ago when I first set up this array on my home
> theater pc. Until now I had no idea about the cron job - I'll make
> sure to implement that. I am preparing to move to 6 tb disks sometime
> soon and i'll definitely go enterprise this time.
>
> Regarding the drive timeout: I understand that I need to increase it
> from 30 seconds to something larger (2+ min) but am unaware how to do
> this. Is it a kernel variable? I'll keep googling but this seems like
> it's whats going to save me.
>
> tl;dr: How do I change the drive timeout?
Put something like this in /etc/rc.local or wherever your distro suggests:
for x in /sys/block/sd[a-f]/device/timeout ; do
echo 180 > $x
done
Where the [a-f] is adjusted to suit your needs, and only for non-raid
non-scterc drives.
Phil
next prev parent reply other threads:[~2015-02-11 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 4:20 Wierd: Degrading while recovering raid5 Kyle Logue
2015-02-10 7:35 ` Adam Goryachev
2015-02-10 13:51 ` Phil Turmel
2015-02-10 21:50 ` Kyle Logue
2015-02-11 2:14 ` Phil Turmel [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-11 6:23 Kyle Logue
2015-02-11 14:28 ` Phil Turmel
2015-02-11 22:12 ` Kyle Logue
2015-02-12 0:15 ` Phil Turmel
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=54DABAFD.6070101@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=teque5@gmail.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;
as well as URLs for NNTP newsgroup(s).