From: Tejun Heo <tj@kernel.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org
Subject: Re: libata timeouts when stressing a Samsung HDD
Date: Thu, 19 Feb 2009 15:21:38 +0900 [thread overview]
Message-ID: <499CFA72.1040905@kernel.org> (raw)
In-Reply-To: <20090216163040.194f5389@dhcp-100-2-144.bos.redhat.com>
Hello,
Chuck Ebbert wrote:
>> Yeap, SD_TIMEOUT should be it. But I've never personally seen disk
>> flushing taking as long as 30 seconds. Does it really happen? It's
>> not like the drive would be doing random seeking. One full stroke
>> across the platter should be it. Even with the rotational delay,
>> going over 30 seconds doesn't seem very likely.
>
> I just noticed that the other drive, a Western Digital, was using 1.5Gbps
> instead of 3.0. So I forced the Samsung to the slower speed and now I
> can't make the timeout happen anymore.
Timeouts are much more likely with the higher transfer speed but it's
kind of strange for flush cache to be affected by it as the command
doesn't have any data to transfer. :-(
--
tejun
next prev parent reply other threads:[~2009-02-19 6:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 21:40 libata timeouts when stressing a Samsung HDD Chuck Ebbert
2009-02-11 1:30 ` Tejun Heo
2009-02-11 4:08 ` Mark Lord
2009-02-11 20:29 ` Chuck Ebbert
2009-02-11 22:03 ` Mark Lord
2009-02-11 22:11 ` Jeff Garzik
2009-02-11 22:29 ` Mark Lord
2009-02-11 22:54 ` Chuck Ebbert
2009-02-12 16:10 ` Mark Lord
2009-02-12 16:13 ` Mark Lord
2009-02-16 3:12 ` Tejun Heo
2009-02-16 21:30 ` Chuck Ebbert
2009-02-19 6:21 ` Tejun Heo [this message]
2009-02-19 16:41 ` Greg Freemyer
2009-02-20 0:33 ` Tejun Heo
2009-02-12 4:28 ` Robert Hancock
2009-02-19 15:27 ` Mark Lord
2009-02-20 0:32 ` Tejun Heo
2009-02-20 2:52 ` Robert Hancock
2009-02-20 3:26 ` Tejun Heo
2009-03-01 19:31 ` Robert Hancock
2009-03-01 20:28 ` Alan Cox
2009-02-11 20:24 ` Chuck Ebbert
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=499CFA72.1040905@kernel.org \
--to=tj@kernel.org \
--cc=cebbert@redhat.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--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).