Bob Frey wrote:
>
> On Wed, Mar 14, 2001 at 09:35:43PM -0500, Pete Zaitcev wrote:
> > 16384 LUNs for Fibre Channel. As you see, scanning is out of the
> > question. You must issue REPORT LUNs and fall back on scanning
> > if the device reports a check condition. I did that when I worked
> Why wai
On Wed, Mar 14, 2001 at 09:35:43PM -0500, Pete Zaitcev wrote:
> 16384 LUNs for Fibre Channel. As you see, scanning is out of the
> question. You must issue REPORT LUNs and fall back on scanning
> if the device reports a check condition. I did that when I worked
Why wait for a check condition? Ther
Doug Ledford wrote:
> Patches welcomed. The one I sent already works on a fiber channel setup (the
> qla2x00 in question is fc and so is the Clariion array it's connected to, no
> detrimental side effects from scanning the box) and so I'm not inclined to add
> a REPORT LUNs section to the code u
Pete Zaitcev wrote:
>
> > Date: Wed, 14 Mar 2001 21:28:14 -0500
> > From: Doug Ledford <[EMAIL PROTECTED]>
>
> > A bug report I was charged with fixing (qla2x00 driver doesn't see all luns or
> > sees multiple identical luns in different scenarios) was not a bug in the
> > qla2x00 driver. [...]
On Thu, Mar 15, 2001 at 02:09:36AM +0100, Björn Stenberg wrote:
> I have also added a definition of the very frequently used INQUIRY response
> data struct. It is currently duplicated in about a dozen different drivers
> and every new driver has to define it yet again. Better to have it in a
> cen
> Date: Wed, 14 Mar 2001 21:28:14 -0500
> From: Doug Ledford <[EMAIL PROTECTED]>
> A bug report I was charged with fixing (qla2x00 driver doesn't see all luns or
> sees multiple identical luns in different scenarios) was not a bug in the
> qla2x00 driver. [...]
> The bug is that we were detect
A bug report I was charged with fixing (qla2x00 driver doesn't see all luns or
sees multiple identical luns in different scenarios) was not a bug in the
qla2x00 driver. The recent changes to allow max luns in the mid layer to be >
7 seems to have caused this problem. However, the proper fix is
Howdy, Linux SCSI folks. I'm working with a friend who recently moved
his Linux box from Red Hat to Debian, and in the process upgraded the
kernel to 2.4.2.
He's running software RAID5 on his QLogic ISP2100 Fibre Channel card,
hooked up to a 6-disk fibre channel shelf, and when he did a full
bac
Here's a suggestion for changes in the scsi.h include file. I have added a
few missing opcodes and some missing device types.
I have also added a definition of the very frequently used INQUIRY response
data struct. It is currently duplicated in about a dozen different drivers
and every new driver
Eric --
Did you ever get a chance to work up these patches and test them?
Matt
On Fri, Feb 16, 2001 at 09:28:16AM -0500, Eric Youngdale wrote:
> >rm... how about something like this:
> >
> >We add a field to the Scsi_Host structure which would indicate if they are
> >SCSI-III able. By default,
10 matches
Mail list logo