From: "Michał Sawicz" <michal@sawicz.net>
To: Phil Turmel <philip@turmel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
Date: Mon, 07 Oct 2013 00:11:05 +0200 [thread overview]
Message-ID: <5251DFF9.4050708@sawicz.net> (raw)
In-Reply-To: <5251D9AF.9030402@turmel.org>
On 06.10.2013 23:44, Phil Turmel wrote:
> The answer is*NO*. That is not expected. But it does happen with
> timeout mismatches, and the double failure you experienced is a common
> result of error correction timeout mismatch. Timeout mismatch is where
> your drives are internally trying to retry reading a bad sector long
> after the OS has given up. It is always associated with consumer-grade
> hard drives in raid arrays.
Right, I knew that consumer HDDs did that, but didn't expect this to
cause such mayhem. So the take out for me for this is: as soon as you
see bad blocks on the drive, fail it, otherwise the whole array will
probably get kicked out sooner or later. Or try and manually force the
drive to reallocate, and then do a scrub.
> You might want to search the list archives for various combinations of
> "error recovery", "scterc", "URE" and "timeout mismatch" for a full
> description of the problem and the recommended ways to avoid it.
Thanks, will do.
--
Michał (Saviq) Sawicz <michal@sawicz.net>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-06 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 23:23 Help with data recovery - RAID6 with 2 failed drives and another with broken sectors Michał Sawicz
2013-10-01 19:24 ` Michał Sawicz
2013-10-06 21:44 ` Phil Turmel
2013-10-06 22:11 ` Michał Sawicz [this message]
2013-10-06 22:15 ` Phil Turmel
2013-10-06 22:56 ` Michał Sawicz
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=5251DFF9.4050708@sawicz.net \
--to=michal@sawicz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.