On Tue, 06 Mar 2007 19:04:28 +0100, Olaf Hering wrote: > > Upcoming IBM pSeries firmware can boot from iscsi. To configure the > openfirmware boot-device string, we need to construct a correct > devicepath. This path includes the lun. Its currently not 100% clear > how exactly this lun value has to look like. > > sg_luns may be the tool to get the value. But its current output is not > parseable by scripts. It even gives the same output for two different > scsi devices: > > girgendwas:~ # lsscsi > [0:0:0:0] disk DGC RAID 5 0219 /dev/sda > [0:0:0:1] disk DGC RAID 5 0219 /dev/sdb > [0:0:0:2] disk DGC RAID 5 0219 /dev/sdc > [0:0:0:3] disk DGC RAID 5 0219 /dev/sdd > girgendwas:~ # sg_luns -V > sg_luns: version: 1.05 20060127 > girgendwas:~ # sg_luns /dev/sdd > Lun list length = 32 which imples 4 lun entries > Report luns [select_report=0]: > 0000000000000000 > 0001000000000000 > 0002000000000000 > 0003000000000000 > girgendwas:~ # sg_luns /dev/sdc > Lun list length = 32 which imples 4 lun entries > Report luns [select_report=0]: > 0000000000000000 > 0001000000000000 > 0002000000000000 > 0003000000000000 > > Is it possible to print the lun only for the requested scsi device? In the simple test I did on pseries, I just determined the boot device, and passed that path to sg_luns. For pseries, there will be only a single lun for boot. At least for the time being primary storage will be on another (possibly raid/lvm) device. So to me, using sg_luns |tail -1 should get the line with the singleton lun in it, albeit with some amount of leading whitespace. Can you extract some value from the installer that will give you the path to the target? ++doug - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
