From: Kai Stian Olstad <raid+list@olstad.com>
To: Alexander Shenkin <al@shenkin.org>,
Phil Turmel <philip@turmel.org>,
Reindl Harald <h.reindl@thelounge.net>,
Carsten Aulbert <carsten.aulbert@aei.mpg.de>,
linux-raid@vger.kernel.org
Subject: Re: SMART detects pending sectors; take offline?
Date: Thu, 12 Oct 2017 17:19:22 +0200 [thread overview]
Message-ID: <07bc0599-df85-17c1-2cec-068bc5b2caec@olstad.com> (raw)
In-Reply-To: <2ab868eb-3ce3-f01b-ac9e-23358563040c@shenkin.org>
On 12. okt. 2017 11:50, Alexander Shenkin wrote:
> On 10/11/2017 6:10 PM, Phil Turmel wrote:
>> You'll need to set your hangcheck timer to 180 seconds, too. I'm not
>> sure how to do that. (I've never seen this particular combination, but
>> it would be another black mark on desktop drives in raid arrays.)
>
> Thanks Phil... Googling around, I haven't found a way to change it
> either, but then again, I'm not really sure what to search for.
Your dmesg did say
[4038193.380526] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
I guess 0 disables this feature or you could just use "echo 180" or
"sysctl kernel.hung_task_timeout_secs = 180".
--
Kai Stian Olstad
next prev parent reply other threads:[~2017-10-12 15:19 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 7:48 SMART detects pending sectors; take offline? Alexander Shenkin
2017-10-07 8:21 ` Carsten Aulbert
2017-10-07 10:05 ` Alexander Shenkin
2017-10-07 17:29 ` Wols Lists
2017-10-08 9:19 ` Alexander Shenkin
2017-10-08 9:49 ` Wols Lists
2017-10-09 20:16 ` Phil Turmel
2017-10-10 9:00 ` Alexander Shenkin
2017-10-10 9:11 ` Reindl Harald
2017-10-10 9:56 ` Alexander Shenkin
2017-10-10 12:55 ` Phil Turmel
2017-10-11 10:31 ` Alexander Shenkin
2017-10-11 17:10 ` Phil Turmel
2017-10-12 9:50 ` Alexander Shenkin
2017-10-12 11:01 ` Wols Lists
2017-10-12 13:04 ` Phil Turmel
2017-10-12 13:16 ` Alexander Shenkin
2017-10-12 13:21 ` Mark Knecht
2017-10-12 15:16 ` Edward Kuns
2017-10-12 15:52 ` Edward Kuns
2017-10-15 14:41 ` Alexander Shenkin
2017-12-18 15:51 ` Alexander Shenkin
2017-12-18 16:09 ` Phil Turmel
2017-12-19 10:35 ` Alexander Shenkin
2017-12-19 12:02 ` Phil Turmel
2017-12-21 11:28 ` Alexander Shenkin
2017-12-21 11:38 ` Reindl Harald
2017-12-23 3:14 ` Brad Campbell
2018-01-03 12:44 ` Alexander Shenkin
2018-01-03 13:26 ` Brad Campbell
2018-01-03 13:50 ` Alexander Shenkin
2018-01-03 15:53 ` Phil Turmel
2018-01-03 15:59 ` Alexander Shenkin
2018-01-03 16:02 ` Phil Turmel
2018-01-04 10:37 ` Alexander Shenkin
2018-01-04 12:28 ` Alexander Shenkin
2018-01-04 13:16 ` Brad Campbell
2018-01-04 13:39 ` Alexander Shenkin
2018-01-05 5:20 ` Brad Campbell
2018-01-05 5:25 ` Brad Campbell
2018-01-05 10:10 ` Alexander Shenkin
2018-01-05 10:32 ` Brad Campbell
2018-01-05 13:50 ` Phil Turmel
2018-01-05 14:01 ` Alexander Shenkin
2018-01-05 15:59 ` Wols Lists
2017-10-12 15:19 ` Kai Stian Olstad [this message]
2017-10-10 22:23 ` josh
2017-10-11 6:23 ` Alexander Shenkin
2017-10-10 9:21 ` Wols Lists
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=07bc0599-df85-17c1-2cec-068bc5b2caec@olstad.com \
--to=raid+list@olstad.com \
--cc=al@shenkin.org \
--cc=carsten.aulbert@aei.mpg.de \
--cc=h.reindl@thelounge.net \
--cc=linux-raid@vger.kernel.org \
--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 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).