From: Phil Turmel <philip@turmel.org>
To: yuji_touya@yokogawa-digital.com, swmike@swm.pp.se
Cc: linux-raid@vger.kernel.org
Subject: Re: Help raid10 recovery from 2 disks removed
Date: Thu, 24 Oct 2013 08:16:50 -0400 [thread overview]
Message-ID: <52690FB2.6000005@turmel.org> (raw)
In-Reply-To: <1F36A02C60ACD1478457DCD917DA0FA8034983@ZEX001-0M9030.jp.ykgw.net>
Good morning,
On 10/24/2013 06:14 AM, yuji_touya@yokogawa-digital.com wrote:
> Mikael,
[trim /]
>> You need to figure out what happened to get sdb kicked out of the array,
>> check logs and "dmesg". Also use smartctl to check sdb and see if it's
>> failing.
[trim /]
> Device Model: ST2000DM001-9YN164
If I recall correctly, this model doesn't support error recovery
control. If you haven't fixed your driver timeouts, it explains your
situation.
> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 115 097 006 Pre-fail Always - 88125160
> 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0
> 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 14
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
No reallocations...
> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 112
> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 112
But many sectors waiting for rewrite (which will either fix them or
reallocate them). Rewrites can't succeed in normal MD operation with
mismatched timeouts.
If you search the archives for various combinations of "scterc",
"timeout mismatch", "URE" and "error recovery", you'll find numerous
discussion of this problem and ways to mitigate it. (More like horror
stories, to be honest.) Most importantly, plan to buy RAID-capable
drives in the future.
HTH,
Phil
next prev parent reply other threads:[~2013-10-24 12:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 5:10 Help raid10 recovery from 2 disks removed yuji_touya
2013-10-24 8:54 ` Mikael Abrahamsson
2013-10-24 10:14 ` yuji_touya
2013-10-24 12:16 ` Phil Turmel [this message]
2013-10-25 10:47 ` yuji_touya
2013-10-25 12:07 ` Mikael Abrahamsson
2013-10-25 12:09 ` Phil Turmel
2013-10-24 12:44 ` Mikael Abrahamsson
2013-10-25 7:27 ` Dag Nygren
2013-10-25 8:24 ` Mikael Abrahamsson
2013-10-25 8:34 ` Dag Nygren
2013-10-25 10:08 ` yuji_touya
2013-10-25 12:21 ` Phil Turmel
2013-10-25 16:05 ` Dag Nygren
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=52690FB2.6000005@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=swmike@swm.pp.se \
--cc=yuji_touya@yokogawa-digital.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