Hi Lee, On Sun, 2014-07-27 at 17:55 -0700, Lee Duncan wrote: > On 07/25/2014 04:46 PM, Lee Duncan wrote: > > Hi: > > > > I am creating an iSCSI LUNs using iblock back end storage. > > > > I notice that my VPD Unit Serial Number is different each time my server > > reboots. That does not seem right. > > I take it by the lack of response that this is either an issue that has > been discussed before, or one that nobody else cares about? > > In my case, this bug means that when my target nodes reboot and I get > new Serial Numbers the cluster using that node as part of a logical > volume cannot find it. > > I will work on a patch for submission. > > > > > Is this a bug? > > > > I looked back through the list archives and saw that you do not allow > > this attribute to be set at back store creation time, but there is an > > option to tell it not generate a WWN. (using generate_wwn=false) > > > > But when I do that I get no VPD Page 0x83 data at all, and the name of > > the resulting target, once connected, in /dev/disk/by-id is scsi-1LIO-ORG. > > > > It does not seem right that the identity of the disc changes each time > > the server is rebooted. > > > Can you be a bit more specific about the version of userspace code your using..? For rtslib + targetcli v2, the unit serial is saved via lio-utils for each device into /etc/target/tcm_start.sh, that ends up looking like the following: tcm_node --setunitserialwithmd rd_mcp_1/ramdisk_large 758fe0a4-af72-495a-adf0-afde7926e9a5 For at rtslib + targetcli v3-pre code, this should be getting saved into /etc/target/scsi_target.lio, but IIRC some of the earlier v3 code was not saving /sys/kernel/config/target/core/$HBA/$DEV/wwn/vpd_unit_serial. Jerome (CC'ed), can you confirm if this has been fixed already..? Thanks, --nab -- 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
