Hello, On Wed, Aug 24, 2005 at 11:01:12AM +0100, Christoph Hellwig wrote: > > yes exactly, only the bootdrive LUN is registered after bootup. I have > > to selectively scsiadd the other LUNs if there is a gap between the > > boot LUN (1-8 in our setup) and the shared storages (9-14). I don't > > consider this a bug though, I had to remove some devices otherwise, > > and old drivers had to be patched to allow this at all. > > Actually this sounds like a bug in your storage system. It's probably > reporting to be only SCSI2 complicant, which doesn't make sense for > FC storage. Please try the patch below: [...] Unfortunately this does not fix this issue, besides the SAN being reported as a scsi3 device now. Thanks anyway :) Frederik Schueler -- ENOSIG
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: new qla2xxx driver breaks SAN setup with 2 controllers
- From: Christoph Hellwig <[email protected]>
- Re: new qla2xxx driver breaks SAN setup with 2 controllers
- References:
- new qla2xxx driver breaks SAN setup with 2 controllers
- From: Frederik Schueler <[email protected]>
- Re: new qla2xxx driver breaks SAN setup with 2 controllers
- From: Patrick Mansfield <[email protected]>
- Re: new qla2xxx driver breaks SAN setup with 2 controllers
- From: Frederik Schueler <[email protected]>
- Re: new qla2xxx driver breaks SAN setup with 2 controllers
- From: Christoph Hellwig <[email protected]>
- new qla2xxx driver breaks SAN setup with 2 controllers
- Prev by Date: question on memory barrier
- Next by Date: Re: new qla2xxx driver breaks SAN setup with 2 controllers
- Previous by thread: Re: new qla2xxx driver breaks SAN setup with 2 controllers
- Next by thread: Re: new qla2xxx driver breaks SAN setup with 2 controllers
- Index(es):