From: Thomas Fjellstrom <thomas@fjellstrom.ca>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Phil Turmel <philip@turmel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Recent drive errors
Date: Thu, 21 May 2015 06:45:54 -0600 [thread overview]
Message-ID: <21066296.95yN8USVxi@balsa> (raw)
In-Reply-To: <alpine.DEB.2.02.1505210956210.9487@uplift.swm.pp.se>
On Thu 21 May 2015 09:58:48 AM Mikael Abrahamsson wrote:
> On Tue, 19 May 2015, Thomas Fjellstrom wrote:
> > How many UREs are considered "ok"? Tens, hundreds, thousands, tens of
> > thousands?
>
> I will replace any drive that have developed UNC sectors a few times, so
> I'd say "less than 10".
In this case, it looked like 5 UNC errors for a single sector, and some weird
latency patterns, till I ran badblocks -w on it, then it gave me > 10k
relocated sectors and many thousands more uncorrectable sectors. Before the
badblocks test, it "looked" ok, now It's most definitely dead.
> +1 on the "set kernel timeout to more than 120 seconds". I have this in
> /etc/rc.local:
>
> for x in /sys/block/sd[a-z] ; do
> echo 180 > $x/device/timeout
> done
>
> echo 4096 > /sys/block/md0/md/stripe_cache_size
I presume it's ok to do that even if the drives do ERC/TLER? Just woke up, but
my brain seems to be telling me it shouldn't break anything since the ERC
drives should always return after 7s no matter what...
--
Thomas Fjellstrom
thomas@fjellstrom.ca
next prev parent reply other threads:[~2015-05-21 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 11:08 Recent drive errors Thomas Fjellstrom
2015-05-19 12:34 ` Phil Turmel
2015-05-19 12:50 ` Thomas Fjellstrom
2015-05-19 13:23 ` Phil Turmel
2015-05-19 14:32 ` Thomas Fjellstrom
2015-05-19 14:51 ` Phil Turmel
2015-05-19 16:07 ` Thomas Fjellstrom
2015-05-20 5:38 ` Thomas Fjellstrom
2015-05-21 7:58 ` Mikael Abrahamsson
2015-05-21 12:45 ` Thomas Fjellstrom [this message]
2015-05-22 13:38 ` Mikael Abrahamsson
2015-05-22 14:19 ` Thomas Fjellstrom
2015-05-22 7:07 ` Weedy
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=21066296.95yN8USVxi@balsa \
--to=thomas@fjellstrom.ca \
--cc=linux-raid@vger.kernel.org \
--cc=philip@turmel.org \
--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 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).