From: Brad Campbell <brad@wasp.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata oops 2.6.11-rc4 yesterdays BK
Date: Thu, 17 Feb 2005 00:54:16 +0400 [thread overview]
Message-ID: <4213B2F8.2070800@wasp.net.au> (raw)
In-Reply-To: <4213821D.1030203@pobox.com>
Jeff Garzik wrote:
> Brad Campbell wrote:
>
>> Brad Campbell wrote:
>>
>>> Woke up to this, this morning.
>>> This is yesterdays 2.6.11-rc4 BK + libata BK + libata-dev BK
>>> It was in the middle of a RAID-6 rebuild (scheduled to take about 740
>>> minutes)
>>>
>>
>> Oh well, it appears to be reproducible anyway!
>
>
> Reproducible without the libata-dev patch?
>
> Reproducible with the current libata driver... on an older kernel? Say
> 2.6.11-rc4 libata with 2.6.10.
Both good questions. I'm running 2.6.10-bk10 with the libata and libata-dev trees of that time now
and it has made it through 2 ata timeouts and is 50% rebuilt on a 750 minute rebuild. If that
survives I'll try and dial in some of the other kernels. 11-12 hour test times make it a bit of a
bear to debug!
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)
This 2.6.10-bk10 is the kernel I have been running on my server for a while now (Almost identical
hardware, just 1 less controller and a couple less disks)
bklaptop:~>ssh srv
Linux srv 2.6.10 #2 Mon Jan 10 18:42:45 GST 2005 i686 GNU/Linux
No mail.
Last login: Wed Feb 16 15:03:13 2005 from bklaptop
brad@srv:~$ uptime
00:50:16 up 37 days, 5:40, 5 users, load average: 0.21, 0.27, 0.35
Lucky I have a ready source of failing drives! 29 Maxtors. 1 is dying after 5000 hours and the other
has 119 reallocated blocks after the first 8 hours.. Looking good thus far! <Bletch>.
Regards,
Brad -- Certified (or is that certifiable) libata torture tester.
--
"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-16 20:54 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 [this message]
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
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=4213B2F8.2070800@wasp.net.au \
--to=brad@wasp.net.au \
--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).