From: Paolo Ornati <ornati@fastwebnet.it>
To: Tejun Heo <htejun@gmail.com>
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 09:38:23 +0100 [thread overview]
Message-ID: <20070122093823.1241be05@localhost> (raw)
In-Reply-To: <45B42569.6030902@gmail.com>
On Mon, 22 Jan 2007 11:46:01 +0900
Tejun Heo <htejun@gmail.com> wrote:
> > I don't know. It's a two years old ST380817AS.
> >
> > # smartctl -a -d ata /dev/sda
> >
> > smartctl version 5.36 [x86_64-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> >
> > === 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).
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
next prev parent reply other threads:[~2007-01-22 8:38 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 [this message]
2007-01-22 9:35 ` Tejun Heo
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=20070122093823.1241be05@localhost \
--to=ornati@fastwebnet.it \
--cc=B.Steinbrink@gmx.de \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@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