Adding it to the blacklist worked. Thank you for the help. Heather -----Original Message----- From: Doug Ledford [mailto:[EMAIL PROTECTED]] Sent: Monday, April 16, 2001 10:40 AM To: conway, heather Cc: '[EMAIL PROTECTED]' Subject: Re: LUN skipping in v2.4.x? "conway, heather" wrote: > > Hi Folks, > I'm working with a mixture of v2.2.x and v2.4.x hosts in an FC-SW > environment that requires the host to be able to skip LUNs. I've applied > Eric's linux-2.4.1.diff and Doug's scsi241_ey2.diff patches on different > v2.4.x hosts to address the issue of scanning past LUN 7 on v2.4.x. > Has anyone addressed allowing a v2.4.x Linux host running to skip LUNs? or > to scan past a non-existent target 0 LUN 0? If so, is there a patch > available? > Thanks for your help. You need to add your device IDs to the scsi blacklist with the flag BLIST_SPARSELUN to do what you are wanting (although, currently there is no way around the fact that the linux SCSI subsystem assumes no device exists on a particular target ID if LUN 0 doesn't exist, so it will skip non-exisitent LUNs above 0, but if LUN 0 doesn't exist on that target ID, then nothing on that target ID will get scanned). -- Doug Ledford <[EMAIL PROTECTED]> http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
