linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Russell Sloan <russell.sloan@lingua-data.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: SATA timeout value
Date: Tue, 24 Apr 2007 17:25:51 +0900	[thread overview]
Message-ID: <462DBF0F.1080903@gmail.com> (raw)
In-Reply-To: <32623559.31421177346818776.JavaMail.servlet@perfora>

Russell Sloan wrote:
> Yes, it looks like it's trying very hard to talk to the drive (which
> is a good thing under normal circumstances), but the drive isn't
> there anymore.  It's SATA hardware is powered down at this point.  It
> doesn't sound like the right way of doing things, but it's the
> behavior of the drive I'm working with.
> 
> I actually have a 5-disk RAID that I'm working with, 3 connected
> directly to a SiI 3124 and two behind a 4726 PMP.  The messages for
> the 3 direct connects are the same.  I see similar activity for the 3
> PMP drives.
> 
> Attached is a text file with a complete listing of the activity for
> each of the 5 drives after the command is issued to each.

Ah, right.  After the timeout, libata error handling kicks in and tries
to verify that the drive is there and working.  As the device is
completely unresponsive, it takes some time before libata EH to give up
the device.  I honestly don't know how to solve this.  :-(

-- 
tejun

  parent reply	other threads:[~2007-04-24  8:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-23 16:46 SATA timeout value Russell Sloan
2007-04-23 22:07 ` Mark Lord
2007-04-24  8:25 ` Tejun Heo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-23 15:11 Russell Sloan
2007-04-23 15:50 ` Tejun Heo
2007-04-21 23:24 Russell Sloan
2007-04-23  6:59 ` Tejun Heo

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=462DBF0F.1080903@gmail.com \
    --to=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=russell.sloan@lingua-data.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).