From: Zygo Blaxell <zblaxell@furryterror.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Uncorrectable errors on RAID-1?
Date: Tue, 23 Dec 2014 16:16:09 -0500 [thread overview]
Message-ID: <20141223211605.GC436@hungrycats.org> (raw)
In-Reply-To: <CAJCQCtQ-DkJh5tg1gWuv6EW=enm66jx16jrtXhXiPvhauRnJ9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
On Sun, Dec 21, 2014 at 05:25:47PM -0700, Chris Murphy wrote:
> For the kernel to automatically fix
> bad sectors by overwriting them, the drive needs to explicitly report
> read errors. If the SCSI command timer value is shorter than the
> drive's error recovery, the SATA link might get reset before the drive
> reports the read error and then uncorrected errors will persist
> instead of being automatically fixed.
Is there a way to tell the kernel to go ahead and assume that all timeouts
are effectively read errors? For a simple non-removable hard disk (i.e.
not removable and not optical), that seems like a reasonable workaround
for an assortment of firmware brokenness.
I just did a quick survey of random drives here and found less than 10%
support "smartctl -l scterc". A lot of server drives (or at least the
drives that shipped in servers) don't have it, but laptop drives do.
Drives with firmware that has horrifying known bugs do also have this
feature. :-P
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-12-23 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 19:34 Uncorrectable errors on RAID-1? constantine
2014-12-21 21:56 ` Robert White
2014-12-21 22:17 ` Hugo Mills
2014-12-22 0:25 ` Chris Murphy
2014-12-23 21:16 ` Zygo Blaxell [this message]
2014-12-23 22:09 ` Chris Murphy
2014-12-23 22:23 ` Chris Murphy
2014-12-28 3:12 ` Phillip Susi
2014-12-29 21:53 ` Chris Murphy
2014-12-30 20:46 ` Phillip Susi
2014-12-30 23:58 ` Chris Murphy
2014-12-31 3:16 ` Phillip Susi
2015-01-03 5:31 ` Chris Murphy
2015-01-05 4:18 ` Phillip Susi
2015-01-05 7:41 ` Chris Murphy
2014-12-31 15:40 ` Austin S Hemmelgarn
[not found] ` <CAJCQCtQYhaDEic5bwd+PEcEfwOqLwAe8cT8VPZ9je+JLRP1GPw@mail.gmail.com>
2014-12-22 14:28 ` constantine
2014-12-22 16:05 ` Chris Murphy
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=20141223211605.GC436@hungrycats.org \
--to=zblaxell@furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).