Grzegorz Powiedziuk writes: > [0:0:0:1074675744]disk IBM 2107900 .278 /dev/sda > [0:0:0:1075527712]disk IBM 2107900 .278 /dev/sdb > > I've seen that before. I don't like the LUN number - 1074675744 > Make sure that in your ZFCP you have it right. > I've seen bogus numbers like this when I typed too many zeros in the LUN > numbe field.
Those are normal LUN numbers for DS8k and similar scsimask-style LUNs. Unlike V7000, XIV, SVC etc which start at LUN ids [0, ], 1, 2, 3 for each host, a DS8k assigns a unique 4-hex-digit volume ID 0xWXYZ for every volume it creates (whether ECKD or SCSI) and for scsimask-mode host connections (such as the Linux one above) to a DS8k volume group containing volume ID 0xWXYZ it makes it visible as LUN id 0x40WX40YZ00000000. In the above list, Linux maps it to the old-style "host:bus:target:lun" by using for the LUN those upper 8 hex digits (first 32 bits of the 64-bit LUN). 1074675744 is 0x400e4020 and 1075527712 is 0x401b4020 so those are valid LUN numbers for the what the DS8k would refer to as volume ids 0x0e02 and 0x1b20 (in extent pools 0 and 1 respectively by looking at the first hex digit of each). --Malcolm -- Malcolm Beattie Linux and System z Technical Consultant, zChampion IBM UK Systems and Technology Group ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
