linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: ata_eh_link_autopsy:  Bug?
Date: Tue, 01 May 2012 19:52:33 -0400	[thread overview]
Message-ID: <4FA07741.1030105@teksavvy.com> (raw)
In-Reply-To: <4FA07655.6090506@teksavvy.com>

On 12-05-01 07:48 PM, Mark Lord wrote:
> On 12-05-01 05:58 PM, Tejun Heo wrote:
>> On Tue, May 01, 2012 at 04:27:00PM -0400, Mark Lord wrote:
>>> MMmm.. even that isn't good enough, because the first ATA_QCFLAG_IO test
>>> bypasses the rest of that logic and triggers unconditional retries.  Ugh.
>>
>> Hmmm... the unconditional retry on ATA_QCFLAG_IO is intenttional so
>> that known good requests from FS are guaranteed to be retried no
>> matter how whacky the underlying device is.  I'm not sure whether that
>> was a good decision tho.  Maybe we should trust the hardware a bit
>> more.  So, I'm not necessarily against changing it.
> 
> With multi-terabyte drives being commonplace now, bad sectors seem
> to be a more frequent occurrence than I can remember from the past.
> 
> And when libata stumbles across a bad sector, it literally hangs the
> machine for _minutes_ doing retries.  I have never seen a retry make
> any difference whatsoever on a bad sector read.  New, old, or ancient hardware.


And as a reminder to anyone else listening in,
it's easier than you might think to test failure paths like this.

Here, I keep a few 300GB drives around just for that purpose,
and use "hdparm --make-bad-sector" on them to inject media errors
at specific places on the disk or filesystem.

Cheers

  reply	other threads:[~2012-05-01 23:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 20:12 ata_eh_link_autopsy: Bug? Mark Lord
2012-05-01 20:27 ` Mark Lord
2012-05-01 21:58   ` Tejun Heo
2012-05-01 23:48     ` Mark Lord
2012-05-01 23:52       ` Mark Lord [this message]
2012-05-02  0:00       ` [PATCH] libata-eh don't waste time retrying media errors Mark Lord
2012-05-02  3:03         ` [PATCH] libata-eh don't waste time retrying media errors (v2) Mark Lord
2012-05-02 15:54           ` Tejun Heo
2012-05-02 19:10             ` Mark Lord
2012-05-02 19:22             ` [PATCH] libata-eh don't waste time retrying media errors (v3) Mark Lord
2012-05-02 19:33               ` Tejun Heo
2012-05-02 19:43                 ` Mark Lord
2012-05-02 19:46                   ` Tejun Heo
2012-05-04  2:25                     ` Jeff Garzik
2012-05-04  3:04                       ` Mark Lord

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=4FA07741.1030105@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@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).