Re: ZFCP lun status command?
If I had only thought to do that FIRST! I would have found them if so. I had done a lszfcp -D to list the active luns on all the servers, but these were not active (yet there under /sys under the fcp devs). I thought for sure it would be a server with them active - doh! Thanks! -- *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 4:08 PM, Mark Post wrote: > >>> On 2/15/2016 at 03:19 PM, James Vincent > wrote: > > Basically, I can't list the luns at all. The exact same thing done on > the > > other CEC results in showing me all the luns (non-NPIV). > > > > Strange(r) thing is that the servers currently have luns working okay - > all > > paths online. The one server we were trying to get a lun on, I tried > > others and got one to work okay. > > Just out of curiosity, I would check all your systems for LUN > 0xc101 under /sys/bus/ccw/devices/0.0.$HBA/0x$WWPN/ > > If you find it, echo 0xc101 into unit_remove and see what > happens. > > > I'm thinking I need to open a problem but with whom is a question (CP?) > > If the above is your situation, and the echo command fixes it, open it > with your Linux service provider. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
Thanks Alan, you triggered an old brain-cell. A while ago I remembered a server that was having fits with its LVM, so the Linux guy gave it new luns and re-build the LVM structures, copied the data (as much as could be) - then clean up the old luns. But I remember an issue in cleaning up and he may have been over zealous. Looking back through the SAN Admin DB logs we have, they are in fact the ones causing issues. So I have the server and FCPs that are the culprits. And sure enough, they were still there in /sys... (although lszfcp -D didn't report them) Sending the luns to unit_remove did the trick. Wow - a fun adventure! I wish there were an easier to find the right trail, but it is solved now. The SCSIDISC not reporting luns is a whole other issue... -- *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 3:52 PM, Alan Altmark wrote: > On Monday, 02/15/2016 at 08:36 GMT, James Vincent > wrote: > > HCPRXS977I The utility LUN on WWPN 5973001C8D9C and virtual FCP > device > > 0101 could not be opened > > HCPRXS976I WWPN 5973001C8D9C on virtual FCP device 0101 ignored > > MIF C in CSS 2 opened a connection to the LUN on a non-NPIV adapter and > never closed it. What you need is the subchannel (device number) that > opened the connection. That would lead you to the virtual machine. > > I would probably start with the firmware folks to find out how to > determine the subchannel that has the connection open. > > NPIV makes this problem go away since each subchannel uses its own local > WWPN. > > Alan Altmark > > Senior Managing z/VM and Linux Consultant > Lab Services System z Delivery Practice > IBM Systems & Technology Group > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > alan_altm...@us.ibm.com > IBM Endicott > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
>>> On 2/15/2016 at 03:19 PM, James Vincent >>> wrote: > Basically, I can't list the luns at all. The exact same thing done on the > other CEC results in showing me all the luns (non-NPIV). > > Strange(r) thing is that the servers currently have luns working okay - all > paths online. The one server we were trying to get a lun on, I tried > others and got one to work okay. Just out of curiosity, I would check all your systems for LUN 0xc101 under /sys/bus/ccw/devices/0.0.$HBA/0x$WWPN/ If you find it, echo 0xc101 into unit_remove and see what happens. > I'm thinking I need to open a problem but with whom is a question (CP?) If the above is your situation, and the echo command fixes it, open it with your Linux service provider. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
On Monday, 02/15/2016 at 08:36 GMT, James Vincent wrote: > HCPRXS977I The utility LUN on WWPN 5973001C8D9C and virtual FCP device > 0101 could not be opened > HCPRXS976I WWPN 5973001C8D9C on virtual FCP device 0101 ignored MIF C in CSS 2 opened a connection to the LUN on a non-NPIV adapter and never closed it. What you need is the subchannel (device number) that opened the connection. That would lead you to the virtual machine. I would probably start with the firmware folks to find out how to determine the subchannel that has the connection open. NPIV makes this problem go away since each subchannel uses its own local WWPN. Alan Altmark Senior Managing z/VM and Linux Consultant Lab Services System z Delivery Practice IBM Systems & Technology Group ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
A bit more info: I ran SCSIDISC on all my LPARs. On the CEC that is giving me issues with some luns, I get: For virtual FCP device 0101 Please choose a number corresponding to a WWPN, 'ALL' to select all WWPNs or 'QUIT' 0) 5973001C8D9C 1) C05076E51A803801 0 HCPRXS977I The utility LUN on WWPN 5973001C8D9C and virtual FCP device 0101 could not be opened HCPRXS976I WWPN 5973001C8D9C on virtual FCP device 0101 ignored Storage area network analysis complete Basically, I can't list the luns at all. The exact same thing done on the other CEC results in showing me all the luns (non-NPIV). Strange(r) thing is that the servers currently have luns working okay - all paths online. The one server we were trying to get a lun on, I tried others and got one to work okay. I'm thinking I need to open a problem but with whom is a question (CP?) -- *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 1:50 PM, James Vincent wrote: > Understood - thank you for the info. > > The lszfcp -Da doesn't return anything though for that lun because the lun > is not "active". It is in the fcp devices > (/sys/bus/ccw/devices/0.0.0100/0x5973001c8d9c) but other than that, no > other command will show anything on it. > > > -- *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:59 AM, Benjamin Block < > bbl...@linux.vnet.ibm.com> wrote: > >> Hej James, >> >> On 09:13 Mon 15 Feb , 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 0x000e 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 >> >> As Note: It will probably not make your case better, but for future >> reference, please use the method described in the RHEL manual >> [1]. In other words: use the uevent trigger (this will safe you >> trouble in case Redhat ever extends those udev-rules and >> only calling zfcpconf.sh is not enough anymore). Still, the >> zfcpconf.sh script is not programmed to do any error-reporting. >> Depending on the error, it should be visible in the syslog >> though. >> >> > 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/0x5973001c8d9c/ and noted both >> > luns are there; looked in the 0x000e directory and failed >> is 1 >> > and status is 0x6080 So the lun didn't get added as a device, but >> > nothing told us that - no errors/msgs at all. >> > >> > 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) >> >> Strictly spoken, this is not the intended Usecase for lsluns. Rather, >> lsluns is for discovering LUNs that are accessible for your machine, not >> what is already attached. >> >> > >> > Does anyone have an idea of how to show lun status info like this >> easier? >> > >> >> `lszfcp -D' will show all SCSI devices that zfcp currently knows of (in >> much the same way as you discovered it). It doesn't show whether the >> device is online and operational though. For that you can either call it >> with the -a switch `lszfcp -Da --lun=0x5022', this will show >> you the attributes of the device (you want to look at 'zfcp_failed' and >> 'state'). Or you can use the output of lszfcp as input for the `lsscsi' >> tool (a standard linux-tool), for example `lsscsi -dL 3:0:1:25', which >> also prints the state-information (the same as in lszfcp). >> >> Thats the best ways I can remember just now. >> >> >> >> [1] - >> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/ >> >> 7/html/Installation_Guide/sect-post-installation-fcp-attached-luns-s390 >> .html#sect-post-installation-fcp-attached-luns-persistent-s390 >> >> >> Beste Grüße / Best >> regards, >> - Benjamin Block >> -- >> Linux on z Systems Development / IBM Systems & Technology >> Group >>
Re: ZFCP lun status command?
Understood - thank you for the info. The lszfcp -Da doesn't return anything though for that lun because the lun is not "active". It is in the fcp devices (/sys/bus/ccw/devices/0.0.0100/0x5973001c8d9c) but other than that, no other command will show anything on it. -- *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:59 AM, Benjamin Block wrote: > Hej James, > > On 09:13 Mon 15 Feb , 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 0x000e 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 > > As Note: It will probably not make your case better, but for future > reference, please use the method described in the RHEL manual > [1]. In other words: use the uevent trigger (this will safe you > trouble in case Redhat ever extends those udev-rules and > only calling zfcpconf.sh is not enough anymore). Still, the > zfcpconf.sh script is not programmed to do any error-reporting. > Depending on the error, it should be visible in the syslog > though. > > > 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/0x5973001c8d9c/ and noted both > > luns are there; looked in the 0x000e directory and failed is > 1 > > and status is 0x6080 So the lun didn't get added as a device, but > > nothing told us that - no errors/msgs at all. > > > > 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) > > Strictly spoken, this is not the intended Usecase for lsluns. Rather, > lsluns is for discovering LUNs that are accessible for your machine, not > what is already attached. > > > > > Does anyone have an idea of how to show lun status info like this easier? > > > > `lszfcp -D' will show all SCSI devices that zfcp currently knows of (in > much the same way as you discovered it). It doesn't show whether the > device is online and operational though. For that you can either call it > with the -a switch `lszfcp -Da --lun=0x5022', this will show > you the attributes of the device (you want to look at 'zfcp_failed' and > 'state'). Or you can use the output of lszfcp as input for the `lsscsi' > tool (a standard linux-tool), for example `lsscsi -dL 3:0:1:25', which > also prints the state-information (the same as in lszfcp). > > Thats the best ways I can remember just now. > > > > [1] - > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/ > > 7/html/Installation_Guide/sect-post-installation-fcp-attached-luns-s390 > .html#sect-post-installation-fcp-attached-luns-persistent-s390 > > > Beste Grüße / Best > regards, > - Benjamin Block > -- > Linux on z Systems Development / IBM Systems & Technology > Group > IBM Deutschland Research & Development GmbH > Vorsitz. AufsR.: Martina Koederitz /Geschäftsführung: Dirk > Wittkopp > Sitz der Gesellschaft: Böblingen / Registergericht: AmtsG Stuttgart, HRB > 243294 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
They are looking at what they can, but as far as they can tell there is nothing locked or showing in use someplace. He punted back to us as a "z" thing thinking one of the other servers has it, but from our scanning we don't see it. -- *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 1:48 PM, Mark Post wrote: > >>> On 2/15/2016 at 01:40 PM, James Vincent > wrote: > > 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"? > > Would the storage admin be able to tell you that? (Not familiar enough > with that end of things to know if it show information like that.) > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
>>> On 2/15/2016 at 01:40 PM, James Vincent >>> wrote: > 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"? Would the storage admin be able to tell you that? (Not familiar enough with that end of things to know if it show information like that.) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
Aha! Missed this in dmesg: zfcp 0.0.0100: LUN 0xe on port 0x5973001c8d9c 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 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 0x000e 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/0x5973001c8d9c/ and noted both >> luns are there; looked in the 0x000e directory and failed is 1 >> and status is 0x6080 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?: > > ": LUN 0x on port 0x is > already in use by CSS, MIF Image ID 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
Hej James, On 09:13 Mon 15 Feb , 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 0x000e 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 As Note: It will probably not make your case better, but for future reference, please use the method described in the RHEL manual [1]. In other words: use the uevent trigger (this will safe you trouble in case Redhat ever extends those udev-rules and only calling zfcpconf.sh is not enough anymore). Still, the zfcpconf.sh script is not programmed to do any error-reporting. Depending on the error, it should be visible in the syslog though. > 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/0x5973001c8d9c/ and noted both > luns are there; looked in the 0x000e directory and failed is 1 > and status is 0x6080 So the lun didn't get added as a device, but > nothing told us that - no errors/msgs at all. > > 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) Strictly spoken, this is not the intended Usecase for lsluns. Rather, lsluns is for discovering LUNs that are accessible for your machine, not what is already attached. > > Does anyone have an idea of how to show lun status info like this easier? > `lszfcp -D' will show all SCSI devices that zfcp currently knows of (in much the same way as you discovered it). It doesn't show whether the device is online and operational though. For that you can either call it with the -a switch `lszfcp -Da --lun=0x5022', this will show you the attributes of the device (you want to look at 'zfcp_failed' and 'state'). Or you can use the output of lszfcp as input for the `lsscsi' tool (a standard linux-tool), for example `lsscsi -dL 3:0:1:25', which also prints the state-information (the same as in lszfcp). Thats the best ways I can remember just now. [1] - https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/ 7/html/Installation_Guide/sect-post-installation-fcp-attached-luns-s390 .html#sect-post-installation-fcp-attached-luns-persistent-s390 Beste Grüße / Best regards, - Benjamin Block -- Linux on z Systems Development / IBM Systems & Technology Group IBM Deutschland Research & Development GmbH Vorsitz. AufsR.: Martina Koederitz /Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: AmtsG Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
Re: ZFCP lun status command?
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 0x000e 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/0x5973001c8d9c/ and noted both luns are there; looked in the 0x000e directory and failed is 1 and status is 0x6080 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?: ": LUN 0x on port 0x is already in use by CSS, MIF Image ID 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 lists...@vm.marist.edu 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/
ZFCP lun status command?
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 0x000e 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/0x5973001c8d9c/ and noted both luns are there; looked in the 0x000e directory and failed is 1 and status is 0x6080 So the lun didn't get added as a device, but nothing told us that - no errors/msgs at all. 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? -- *James Vincent* -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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/
