Messages in this thread | | | Date | Wed, 24 Aug 2005 13:50:22 +0100 | From | Christoph Hellwig <> | Subject | Re: new qla2xxx driver breaks SAN setup with 2 controllers |
| |
On Wed, Aug 24, 2005 at 02:48:03PM +0200, Frederik Schueler wrote: > 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.
Cane you add BLIST_SPARSELUN and BLIST_LARGELUN to the flags aswell?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |