From: Mark Lord <lkml@rtr.ca>
To: Tejun Heo <htejun@gmail.com>
Cc: Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
Paolo Ornati <ornati@fastwebnet.it>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
Date: Sun, 30 Sep 2007 13:43:35 -0400 [thread overview]
Message-ID: <46FFE047.7030102@rtr.ca> (raw)
In-Reply-To: <46FFDCE5.4060900@gmail.com>
Tejun Heo wrote:
> Mark Lord wrote:
>> Jeff Garzik wrote:
>>> Paolo Ornati wrote:
>>>> I have this problem only with XFS, and even with XFS it goes away
>>>> mounting with "nobarrier"...
>>> This last is an interesting datapoint.
>>>
>>> I wonder if libata has a generic problem with NCQ + FLUSH CACHE.
>> Yeah, that's pretty suspicious. Prior to issuing a FLUSH_CACHE op,
>> one must first drain all outstanding NCQ commands (and not issue new ones).
>>
>> I'm sure the code must *try* to do that, but perhaps there's a bug in
>> there?
>> Or just another drive bug?
>
> If there was such a bug, the aborted commands list should contain both
> FPDMA commands and FLUSH commands. I don't think command filtering
> itself is broken. Possibly another quirky firmware but it's strange
> that this is the only Seagate drive showing this problem.
Yeah, that's the strange bit.
Surely someone at SuSE must have a drive like that,
which they could set up with XFS and reproduce the same results?
??
next prev parent reply other threads:[~2007-09-30 17:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 14:05 [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS Paolo Ornati
2007-09-30 14:17 ` Tejun Heo
2007-09-30 14:42 ` Paolo Ornati
2007-09-30 14:29 ` Alan Cox
2007-09-30 14:46 ` Paolo Ornati
2007-09-30 15:05 ` Jeff Garzik
2007-09-30 15:28 ` Paolo Ornati
2007-09-30 15:43 ` Jeff Garzik
2007-09-30 15:52 ` Paolo Ornati
2007-09-30 15:59 ` Jeff Garzik
2007-09-30 16:03 ` Paolo Ornati
2007-09-30 17:26 ` Mark Lord
2007-09-30 17:29 ` Tejun Heo
2007-09-30 17:43 ` Mark Lord [this message]
2007-09-30 17:51 ` Tejun Heo
2007-09-30 18:54 ` Mark Lord
2007-09-30 19:01 ` Mark Lord
2007-10-02 9:19 ` Tejun Heo
2007-10-02 15:40 ` Paolo Ornati
[not found] <fa.ernzRd7lGBTxTXHl/DtyMhz/rPk@ifi.uio.no>
2007-09-30 23:45 ` Robert Hancock
2007-10-01 7:21 ` Paolo Ornati
2007-10-01 8:09 ` Jiri Slaby
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=46FFE047.7030102@rtr.ca \
--to=lkml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.