From: Phil Turmel <philip@turmel.org>
To: Barrett Lewis <barrett.lewis.mitsi@gmail.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Mdadm server eating drives
Date: Fri, 14 Jun 2013 17:24:12 -0400 [thread overview]
Message-ID: <51BB89FC.8050503@turmel.org> (raw)
In-Reply-To: <CAPSPcXh8C87whdXdzWgh97qiwLNZOjSB2OD_nxKCfmRL2GZ=Jg@mail.gmail.com>
On 06/14/2013 05:18 PM, Barrett Lewis wrote:
> I'll definatly do this. When you talk about mismatched timeouts, do
> you mean matched between each of the components (as in
> /sys/block/sdX/device/timeout) or between that driver timeout and some
> device timeout per component? If you mean between components, are my
> timeouts matched now, even though I did not raise the 30 seconds on
> the two drives with ERC?
For each drive, the driver timeout (/sys/block/.../device/timeout) must
be longer than the drive's timeout (smartctl -l scterc).
Note that scterc is in deciseconds, while the driver uses seconds.
Enterprise drives typically power up with 7.0 second timeouts. The few
SSDs I've been playing with power up with 4.0 second timeouts. Without
ERC, the drives I've played with will perform error recovery for about
two full minutes, ignoring the world for the duration.
Phil
next prev parent reply other threads:[~2013-06-14 21:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 13:47 Mdadm server eating drives Barrett Lewis
2013-06-12 13:57 ` David Brown
2013-06-12 14:44 ` Phil Turmel
2013-06-12 15:41 ` Adam Goryachev
[not found] ` <CAPSPcXihHrAi2TB9Fuxb1qOGMc_WzwGoXAA7nHdwe2knkO0LkQ@mail.gmail.com>
[not found] ` <CAPSPcXib4YZ9Ah-jLvL_kPwpKHLxaGT0rNaDL4XQcFm=RtjcAQ@mail.gmail.com>
2013-06-14 0:19 ` Barrett Lewis
2013-06-14 2:08 ` Phil Turmel
[not found] ` <CAPSPcXgMxOF-C2Szu_nf4ZLDC8p+yJFOtvLPu7xy1DTW9VAHjg@mail.gmail.com>
2013-06-14 21:18 ` Barrett Lewis
2013-06-14 21:20 ` Barrett Lewis
2013-06-14 21:25 ` Phil Turmel
2013-06-14 21:30 ` Phil Turmel
2013-06-17 21:37 ` Barrett Lewis
2013-06-18 4:13 ` Mikael Abrahamsson
2013-06-27 0:23 ` Barrett Lewis
2013-06-27 17:13 ` Nicolas Jungers
2013-07-02 0:17 ` Barrett Lewis
2013-07-02 1:57 ` Stan Hoeppner
2013-07-02 15:48 ` Barrett Lewis
2013-07-02 19:44 ` Stan Hoeppner
2013-07-02 19:54 ` Stan Hoeppner
2013-07-02 20:07 ` Jon Nelson
2013-07-02 20:23 ` Stan Hoeppner
2013-07-02 20:58 ` Barrett Lewis
2013-07-03 1:50 ` Stan Hoeppner
2013-07-03 5:26 ` Barrett Lewis
2013-07-03 14:03 ` Jon Nelson
2013-07-03 14:36 ` Phil Turmel
2013-07-03 17:32 ` Stan Hoeppner
2013-07-03 19:47 ` Barrett Lewis
2013-07-03 20:38 ` Jon Nelson
2013-07-04 2:21 ` Stan Hoeppner
2013-07-03 17:05 ` Stan Hoeppner
2013-07-02 21:49 ` Phil Turmel
2013-06-14 21:24 ` Phil Turmel [this message]
2013-07-29 22:25 ` Roy Sigurd Karlsbakk
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=51BB89FC.8050503@turmel.org \
--to=philip@turmel.org \
--cc=barrett.lewis.mitsi@gmail.com \
--cc=linux-raid@vger.kernel.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).