From: Brad Campbell <brad@wasp.net.au>
To: Brad Campbell <brad@wasp.net.au>
Cc: Andy Warner <andyw@pobox.com>, Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org
Subject: Re: libata oops 2.6.11-rc4 yesterdays BK
Date: Sat, 19 Feb 2005 08:14:08 +0400 [thread overview]
Message-ID: <4216BD10.2070008@wasp.net.au> (raw)
In-Reply-To: <42158774.9030406@wasp.net.au>
Brad Campbell wrote:
> Andy Warner wrote:
>
>> Brad Campbell wrote:
>>
>>> [...]
>>> Actually, I'm not sure without the libata dev patch as that removes
>>> SMART support, and I'm not convinced that my smartd polling every 20
>>> minutes does not have something to do with it. All I know is the
>>> older kernel seems to cope. We'll see. 320 minutes left on this
>>> rebuild. I expect it will be done in the morning if all goes
>>> according to plan. (With the 2.6.11 kernel it never survived past
>>> about 25% rebuilt)
>>
>>
>>
>> Can you find time to try it without smartd active ?
>> You report running a uni-processor system, and I have only
>> seen PIO problems with (fast) SMP systems in my testing,
>> but I am forming the opinion that libata-PIO functions
>> are in need of a minor overhaul.
Have been unable to hit the bug with SMART disabled (Kernel unchanged). So...... Pass through (or
SMART in particular) is not really safe on UP either, you just have to work really hard at it to hit
the corner cases.
I can now reproduce it quite reliably with a nasty while ; do loop in bash if anyone has anything
that want's testing.
I'm planning on burning in this box for a while before I put it into production, so I'm not adverse
to blowing it up a little in the mean time.
Regards,
Brad
--
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams
next prev parent reply other threads:[~2005-02-19 4:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 4:28 libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-16 11:01 ` Brad Campbell
2005-02-16 17:25 ` Jeff Garzik
2005-02-16 20:54 ` Brad Campbell
2005-02-16 21:40 ` Andy Warner
2005-02-16 22:47 ` Jeff Garzik
2005-02-16 23:49 ` Andy Warner
2005-02-16 23:58 ` Jeff Garzik
2005-02-17 0:20 ` Andy Warner
2005-02-17 5:08 ` Jeff Garzik
2005-02-17 14:59 ` Andy Warner
2005-02-17 19:13 ` Jeff Garzik
2005-02-17 19:25 ` Andy Warner
2005-02-17 22:36 ` Jeff Garzik
2005-02-17 19:42 ` Which SATA Combos To Consider? Danny Cox
2005-02-17 20:55 ` Jeff Garzik
2005-02-18 0:25 ` Ryan Bourgeois
2005-02-18 0:44 ` Johny Ågotnes
2005-02-18 0:52 ` Jeff Garzik
2005-02-21 23:50 ` Johny Ågotnes
2005-02-21 23:50 ` Johny Ågotnes
2005-02-22 1:55 ` Johny Ågotnes
2005-02-18 6:13 ` libata oops 2.6.11-rc4 yesterdays BK Brad Campbell
2005-02-19 4:14 ` Brad Campbell [this message]
2005-02-21 4:27 ` Brad Campbell
2005-02-22 10:09 ` Brad Campbell
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=4216BD10.2070008@wasp.net.au \
--to=brad@wasp.net.au \
--cc=andyw@pobox.com \
--cc=jgarzik@pobox.com \
--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).