linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: Florian Effenberger <florian@effenberger.org>,
	jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: libata interface fatal error
Date: Thu, 24 May 2007 16:59:52 +0200	[thread overview]
Message-ID: <4655A868.3010707@gmail.com> (raw)
In-Reply-To: <87f94c370705240755t1040e5c8jaeb1882a2a393ac1@mail.gmail.com>

Greg Freemyer wrote:
>> I will try to use another test disk. Right now we use different models
>> of Western Digital "RAID edition".
>>
> 
> iiuc, raid editions are designed to fail fast thus allowing an
> alternate drive to provide the data rather than having to wait thru
> multiple internal retries.
> 
> Could this just be a case of the drive functioning as designed?

If that's the case, the drive should be aborting commands with ICRC bit
set reporting unrecoverable media error (AC_ERR_DEV | AC_ERR_MEDIA in
libata terms) but the errors are fatal interface errors and timeouts,
both of which are indicative of transmission problems on ATA link.

-- 
tejun

  reply	other threads:[~2007-05-24 15:00 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 13:25 libata interface fatal error Florian Effenberger
2007-05-24 13:45 ` Tejun Heo
2007-05-24 14:08   ` Florian Effenberger
2007-05-24 14:21     ` Tejun Heo
2007-05-24 14:47       ` Florian Effenberger
2007-05-24 14:53         ` Tejun Heo
2007-05-24 15:28           ` Florian Effenberger
2007-05-24 14:55         ` Greg Freemyer
2007-05-24 14:59           ` Tejun Heo [this message]
2007-05-24 15:00           ` Florian Effenberger
  -- strict thread matches above, loose matches on Subject: below --
2007-05-26  9:43 Florian Effenberger
2007-05-29  9:16 ` Tejun Heo
2007-05-29 14:16   ` Florian Effenberger
2007-06-06 21:23   ` Florian Effenberger
2007-06-07  9:50     ` Tejun Heo
2007-06-07 14:08       ` Florian Effenberger
2007-06-13 10:37       ` Florian Effenberger
2007-06-14  9:43         ` Tejun Heo
2007-06-14 11:12           ` Florian Effenberger
2007-06-14 12:25             ` Tejun Heo
2007-06-14 15:12               ` Florian Effenberger
2007-06-18  3:10                 ` Tejun Heo
2007-06-18  6:08                   ` Tomi Orava
2007-06-18  6:28                     ` Tejun Heo
2007-06-18 10:38                   ` Florian Effenberger
2007-06-18 10:44                     ` Tejun Heo
2007-06-16 10:23       ` Florian Effenberger
2007-06-18  3:13         ` Tejun Heo
2007-06-18 10:44           ` Florian Effenberger
2007-06-18 10:56             ` Tejun Heo
2007-06-18 11:28               ` Florian Effenberger
2007-06-18 11:30                 ` Tejun Heo
2007-06-18 11:32                   ` Florian Effenberger
2007-06-24 11:32               ` Florian Effenberger
2007-06-25  2:49                 ` Tejun Heo
2007-06-25  8:47                   ` Florian Effenberger
2007-06-18  7:05 Mikael Pettersson
2007-06-18  7:13 ` Tejun Heo
2007-06-18 10:47   ` Florian Effenberger
2007-06-18 17:14 ` Ansgar Knappheide
2007-06-18 18:54 ` Tomi Orava

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=4655A868.3010707@gmail.com \
    --to=htejun@gmail.com \
    --cc=florian@effenberger.org \
    --cc=greg.freemyer@gmail.com \
    --cc=jgarzik@pobox.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).