From: Tejun Heo <htejun@gmail.com>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: "Robert Hancock" <hancockr@shaw.ca>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Jens Axboe" <jens.axboe@oracle.com>,
"Jeff Garzik" <jeff@garzik.org>
Subject: Re: SATA exceptions triggered by XFS (since 2.6.18)
Date: Mon, 22 Jan 2007 18:35:05 +0900 [thread overview]
Message-ID: <45B48549.1080209@gmail.com> (raw)
In-Reply-To: <20070122093823.1241be05@localhost>
Paolo Ornati wrote:
>>> === START OF INFORMATION SECTION ===
>>> Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
>>> Device Model: ST380817AS
>> I'll blacklist it. Thanks.
>
> Ok. It will be better if someone else with the same HD could confirm.
>
> It looks so strange that an HD that works fine, and should support NCQ,
> have so big troubles that I can "freeze" it in less than a second by
> using XFS (while with ext3 I cannot, or at least it's very hard).
Yeap, certainly. I'll ask people first before actually proceeding with
the blacklisting. I'm just getting a bit tired of tides of NCQ firmware
problems.
Anyways, for the time being, you can easily turn off NCQ using sysfs.
Please take a look at http://linux-ata.org/faq.html
--
tejun
next prev parent reply other threads:[~2007-01-22 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 14:29 SATA exceptions triggered by XFS (since 2.6.18) Paolo Ornati
2007-01-21 16:40 ` Paolo Ornati
2007-01-21 17:32 ` Robert Hancock
2007-01-21 19:25 ` Paolo Ornati
2007-01-21 20:32 ` Chr
2007-01-22 0:54 ` Jiri Slaby
2007-01-22 8:16 ` Paolo Ornati
2007-01-22 2:46 ` Tejun Heo
2007-01-22 8:38 ` Paolo Ornati
2007-01-22 9:35 ` Tejun Heo [this message]
2007-01-22 10:02 ` Paolo Ornati
2007-01-22 10:21 ` Paolo Ornati
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=45B48549.1080209@gmail.com \
--to=htejun@gmail.com \
--cc=B.Steinbrink@gmx.de \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--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.