On Fri, Jun 8, 2012 at 10:44 PM, Tregaron Bayly <tregaron@xxxxxxxxxx> wrote: > I believe I recall seeing something like this discussed on the list a few weeks ago. SCST propagates the device handler name > through to the initiator via the "model" field, whereas LIO uses a constant string passed from the backstore module - "IBLOCK", > for instance. The advantage of passing the device handler name through is that if there are multiple luns exported from multiple > targets it's simpler to use naming conventions to sort out where a lun may have come from and what it is for. Below is a patch I > put together to override this constant with the config item name from the storage object and it seems to work in our environment. > > Before: > [root@osd3 mnt]# lsscsi > [0:0:0:0] disk AMCC 9650SE-24M DISK 4.10 /dev/sda > [12:0:0:0] disk LIO-ORG IBLOCK 4.0 /dev/sdb > [12:0:0:1] disk LIO-ORG IBLOCK 4.0 /dev/sdc > > After: > [root@osd3 mnt]# lsscsi > [0:0:0:0] disk AMCC 9650SE-24M DISK 4.10 /dev/sda > [12:0:0:0] disk LIO-ORG san1_backup1 4.0 /dev/sdb > [12:0:0:1] disk LIO-ORG san1_backup2 4.0 /dev/sdc > > Is this functionality possibly useful? Any pitfalls to this approach? The PRODUCT IDENTIFICATION field is assumed to identify a product, not a LUN, isn't it ? Fubo. -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
