On Wed, 2012-10-10 at 07:40 -0400, Brian J. Murrell wrote: > So, understanding that the T10 VPD Binary Device Identifier is what is > given to an initiator as the scsi id of the device, shouldn't this > identifier be 100% persistent and consistent across reboots (or any > other operation) of target server, etc? > Correct. > I am looking at data here, using /dev/disk/by-id/ listings of all my > initiators where the contents of that directory are completely > different from one boot of the target servers to another. > > Before reboot: > lrwxrwxrwx 1 root root 9 Oct 9 21:54 /dev/disk/by-id/scsi-36001405308c88e9d999fd4deddbfe3d1 > lrwxrwxrwx 1 root root 9 Oct 9 21:53 /dev/disk/by-id/scsi-3600140562c4a50cdf918d4a90dadc8de > lrwxrwxrwx 1 root root 9 Oct 9 21:54 /dev/disk/by-id/scsi-360014058da4cbf2d90f3d4404d962ed8 > lrwxrwxrwx 1 root root 9 Oct 9 21:54 /dev/disk/by-id/scsi-36001405cfec437dd2d09d4707da17eda > lrwxrwxrwx 1 root root 9 Oct 9 21:54 /dev/disk/by-id/scsi-36001405f1c9b68fd99c4d4e4ddb9c7d3 > lrwxrwxrwx 1 root root 9 Oct 9 15:32 /dev/disk/by-id/scsi-36001405fa093a96d41d7d4b85dadaadc > > After reboot: > lrwxrwxrwx 1 root root 9 Oct 10 10:24 /dev/disk/by-id/scsi-360014051ceb80a6d86ccd4ec0dbb1ddc > lrwxrwxrwx 1 root root 9 Oct 10 10:24 /dev/disk/by-id/scsi-360014054c23596ad0b46d421ad9791d3 > lrwxrwxrwx 1 root root 9 Oct 10 10:24 /dev/disk/by-id/scsi-3600140562129c33da0d6d4968dae25d3 > lrwxrwxrwx 1 root root 9 Oct 10 10:24 /dev/disk/by-id/scsi-36001405d1f2349bd8bb2d4e56d9ce2d0 > lrwxrwxrwx 1 root root 9 Oct 10 10:24 /dev/disk/by-id/scsi-36001405ede216c8d78f1d4777d8e29d2 > lrwxrwxrwx 1 root root 9 Oct 9 15:32 /dev/disk/by-id/scsi-36001405fa093a96d41d7d4b85dadaadc > > Notice though that one of the six disks did manage to maintain it's > identifier, but the other 5 all changed. > This means the individual /sys/kernel/config/target/core/$HBA/$DEV/wwn/vpd_unit_serial attributes values are not being saved and/or reset between target restart. > Should this really be possible? I wouldn't think it should be. Is > there any situation at all (i.e. have I gotten something misconfigured) > where this can be expected? > How are you saving the running configuration of configfs..? If using your own native rtslib code to setup everything in configfs, then you'll need to _get_wwn() + save the newly generated values for each device after first time creation, and then re-set the saved value using _set_wwn() after subsequent creations with gen_wwn=false. Otherwise you can also use 'saveconfig' from within rtsadmin/targetcli, or use the underlying tcm_dump.tcm_full_backup() from lio-utils to save the running configuration into /etc/target/. --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
