On Mon, Aug 29, 2005 at 12:02:15PM +0200, Andreas Herrmann wrote: > On 29.08.2005 10:48 Christoph Hellwig <[EMAIL PROTECTED]> worte: > > > Never use scsi_add_device with the fc_transport code. > fc_remote_port_add > > will do a proper lun scan if the added rport is a scsi target. > > Won't work for all zSeries FC host adapters because they are > virtualized and you can have several virtual adapters using the same > WWPN/WWNN. Using LUN masking and zoning it is not possible to > configure the SAN such that one virtual adapter sees just that LUNs > that are supposed to be used by it. There is a tool to write an access > control table to the adapter. This ACT specifies which virtual adapter > can access which ports and FCP LUNs ...
Ugly. Maybe we could pass down a bitmap of exluded luns down the scanning path? Starting from fc_rport_create down to scsi_scan_target and the underlying fuctions? - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
