Now that everybody is happy with using the FCP LUN in the SCSI midlayer, this raises a question from the user's perspective:
sysfs and lsscsi display the LUN as decimal number. For the FCP LUN 0x401040c300000000, sysfs and lsscsi display this: $ ls -l /sys/bus/scsi/devices/ total 0 lrwxrwxrwx 1 root root 0 Jun 21 16:49 0:0:0:1086537744 -> ../../../devices/css0/0.0.0010/0.0.181d/host0/rport-0:0-0/target0:0:0/0:0:0:1086537744 $ lsscsi [0:0:0:1086537744]disk IBM 2107900 .270 /dev/sda Asking a system admin to translate the number to hex (0x40C34010) and then swap the pairs to get the real FCP LUN (0x401040c3) is too much. Are there any plans to improve this? Showing the LUN in sysfs as hex number would be the first step. Or does it make more sense to keep the decimal number in sysfs and let tools like lsscsi do the conversion? -- Christof Schmitt - 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
