From: Tejun Heo <htejun@gmail.com>
To: Mike Accetta <maccetta@laurelnetworks.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: ICH6-M libata disk timeouts in 2.6.19 (except with small queue depth)
Date: Sun, 21 Jan 2007 03:21:48 +0900 [thread overview]
Message-ID: <45B25DBC.4020102@gmail.com> (raw)
In-Reply-To: <798.1169174977@mdt.dhcp.pit.laurelnetworks.com>
Mike Accetta wrote:
> The distinguishing factor appears to be the queue depth (4 works, 5
> and various values up to and including 31 fail) not the kernel version.
> I am going to try running with the queue depth clamped at 4 to see if
> this consistently masks the problem. I may also try some more experiments
> if I have the time, like instrumenting what command was issued right
> before the group that all time out or increasing the SCSI timeout,
> in order to get some more insight into what is going on at the time of
> the failure.
Please report the result of 'hdparm -I /dev/sdX' where sdX is the
problematic disk. Quite a few drives have problem with NCQ and we have
to blacklist them.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-01-20 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 23:16 ICH6-M libata disk timeouts 2.6.18 -> 2.6.19 Mike Accetta
2007-01-10 4:56 ` Mike Accetta
2007-01-13 2:23 ` Tejun Heo
2007-01-13 3:09 ` Mike Accetta
2007-01-19 2:49 ` ICH6-M libata disk timeouts in 2.6.19 (except with small queue depth) Mike Accetta
2007-01-20 18:21 ` Tejun Heo [this message]
2007-01-22 16:04 ` Mike Accetta
2007-01-23 3:11 ` Mark Lord
2007-02-27 14:54 ` ICH6-M libata disk timeouts 2.6.18 -> 2.6.19 Tejun Heo
2007-02-27 19:37 ` Mike Accetta
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=45B25DBC.4020102@gmail.com \
--to=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=maccetta@laurelnetworks.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).