Aha! Missed this in dmesg: zfcp 0.0.0100: LUN 0xe000000000000 on port 0x50000973001c8d9c is already in use by CSS2, MIF Image ID c
So that points to another LPAR on the cec and we scanned all the servers on that LPAR, but none have the lun in question (that we can find). I simply did a lszfcp -D on all of them. Any other ideas on what we can do to find who/what has it "in use"? -- *James Vincent* -- President, SHARE Inc. -- Calendar: http://tinyurl.com/JSVCalWeek -- SHARE is an independent volunteer-led information technology association that provides *education*, professional *networking *and industry *influence* On Mon, Feb 15, 2016 at 10:33 AM, Steffen Maier <[email protected]> wrote: > On 02/15/2016 03:13 PM, James Vincent wrote: > >> Does anyone know of a way to get info/status on luns on FCPs that are >> _not_ >> active (failed state)? >> >> This is the scenario: >> zLinux machine with one active lun (non-NPIV) >> A new lun 0x000e000000000000 was added to /etc/zfcp.conf (yes, triple >> checked content for accuracy) >> Ran zfcpconf.sh - no errors, no kernel messages, NO DEVICE added in >> /dev/mapper >> Ran multipath -ll - nothing to report; new lun had no info there >> Ran lsluns - can see the old and new lun in the list (there is a -a flag >> in >> lsluns which shows the active luns, but nothing to show 'failed' luns) >> >> Finally traversed down one of the FCPs >> to /sys/bus/ccw/drivers/zfcp/0.0.0100/0x50000973001c8d9c/ and noted both >> luns are there; looked in the 0x000e000000000000 directory and failed is 1 >> and status is 0x60800000 So the lun didn't get added as a device, but >> > > This status is really only zfcp driver internal for debugging by service > and development and therefore not documented nor should anyone rely on > particular values with stable semantics in here. > > nothing told us that - no errors/msgs at all. >> > > Just a shot in the dark: Did you get a kernel message (dmesg or syslog > (the latter depends on syslog config and might suppress such kernel > message) like the following?: > > "<bus ID of the zfcp device>: LUN 0x<LUN> on port 0x<remote port WWPN> is > already in use by CSS<channel subsystem ID>, MIF Image ID <MIF Image ID of > the LPAR>" > > [ > http://www-01.ibm.com/support/knowledgecenter/linuxonibm/liaaf/lnz_r_km.html > > http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.l0kmsg.doc/l0km_m_zfcp.747e7d.html > ] > > See also the access_denied sysfs attribute description for zfcp units in > our device drivers book. > [SLES12SP1 > http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lhdd/lhdd_t_fcp_wrk_actinfo.html > RHEL7.2 > http://www-01.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.lgdd/lgdd_t_fcp_wrk_actinfo.html > ] > > I was hoping there was something more better to run to tell me that though. >> ie, lsluns -f (for failed) or lsluns -s (to show the full status of the >> luns) >> >> Does anyone have an idea of how to show lun status info like this easier? >> > > After zfcp created the zfcp unit successfully, the next step is scsi > midlayer LUN probing. This can fail, e.g. due to wrong host mapping of the > LUN on the storage server. Unfortunately, Linux does not emit anything in > such case with the default debug levels. > You can debug this further by setting an appropriate scsi_logging_level to > see what the midlayer does and why it fails to finally create a scsi_device > belonging to the zfcp unit. > [ > http://www-05.ibm.com/de/events/linux-on-z/pdf/day2/4_Steffen_Maier_zfcp-best-practices-2015.pdf > ] > > Once there is a scsi_device, and it is of type random access (disk), it > would create a scsi disk device which can then be assembled into a > multipath device. > > -- > Mit freundlichen Grüßen / Kind regards > Steffen Maier > > Linux on z Systems Development > > IBM Deutschland Research & Development GmbH > Vorsitzende des Aufsichtsrats: Martina Koederitz > Geschaeftsfuehrung: Dirk Wittkopp > Sitz der Gesellschaft: Boeblingen > Registergericht: Amtsgericht Stuttgart, HRB 243294 > > ---------------------------------------------------------------------- > 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/ > ---------------------------------------------------------------------- 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/
