From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Patrick Mansfield <patmans@us.ibm.com>,
James Bottomley <James.Bottomley@steeleye.com>
Cc: mikeand@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Broken SCSI code in the BK tree (was: 2.5.59-mm8)
Date: Thu, 06 Feb 2003 18:01:06 -0800 [thread overview]
Message-ID: <293060000.1044583265@[10.10.2.4]> (raw)
In-Reply-To: <20030206172434.A15559@beaverton.ibm.com>
>> > say for sure (if this wasn't related to some SCSI subsystem change,
>> > can I just revert out this section?)
>>
>> No, I'm afraid not. That was just the elimination of those fields from
>> Scsi_Cmnd so now it has to be indirect through cmnd->device. It won't
>> compile without this.
>>
>> James
>
> wli has hit this several times prior to 2.5.59 (months ago), pretty much
> with any across disk IO loads. The driver sets queue depth to 1 for all
> LUNs.
>
> I modified my fsck to run in parallel (well it wasn't running any fsck's
> on non-root disks before that), and am hitting hit it on a NUMAQ box.
Curious. I've no idea why the changes brought this out then ... I've done
hundreds and hundreds of reboots on 2.5 on all sorts of different kernels,
and never, ever seen this. Yet in 2.5.59-bk I see it every single time.
Very odd.
M.
next prev parent reply other threads:[~2003-02-07 1:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 7:31 2.5.59-mm8 Andrew Morton
2003-02-04 8:02 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:05 ` 2.5.59-mm8 Andrew Morton
2003-02-04 8:08 ` 2.5.59-mm8 Joshua Kwan
2003-02-04 8:09 ` 2.5.59-mm8 Martin J. Bligh
2003-02-04 8:17 ` 2.5.59-mm8 Andrew Morton
2003-02-04 22:15 ` Broken SCSI code in the BK tree (was: 2.5.59-mm8) Martin J. Bligh
2003-02-06 5:13 ` Martin J. Bligh
2003-02-06 20:50 ` Martin J. Bligh
2003-02-06 22:30 ` Martin J. Bligh
2003-02-06 23:25 ` James Bottomley
2003-02-07 1:24 ` Patrick Mansfield
2003-02-07 2:01 ` Martin J. Bligh [this message]
2003-02-07 2:25 ` Patrick Mansfield
2003-02-07 4:05 ` Doug Ledford
2003-02-07 4:19 ` Anton Blanchard
2003-02-07 8:50 ` Mike Anderson
2003-02-07 4:19 ` Andrew Morton
2003-02-07 4:24 ` Doug Ledford
2003-02-07 4:35 ` William Lee Irwin III
2003-02-07 4:53 ` Matthew Jacob
2003-02-07 4:50 ` Matthew Jacob
2003-02-07 4:28 ` Martin J. Bligh
2003-02-04 9:07 ` 2.5.59-mm8 Dave Hansen
2003-02-04 9:18 ` 2.5.59-mm8 compile error in tcp_ipv6.c Helge Hafting
2003-02-04 9:21 ` Andrew Morton
2003-02-04 9:29 ` David S. Miller
2003-02-04 9:33 ` 2.5.59-mm8 Arjan van de Ven
2003-02-05 8:08 ` 2.5.59-mm8 Mike Galbraith
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='293060000.1044583265@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeand@us.ibm.com \
--cc=patmans@us.ibm.com \
/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
all inboxes | Powered by JetHome®