Zfcp_san_disc, and many other tools typically only display what Linux 
already knows about.  If you start with the device offline, then it'll 
bring the device online and show you what is currently in the fabric.  If 
you start with the device online, then it shows what is in /sys and that's 
it.  It doesn't try to update anything.

Each device has a file that can be used to rediscover changes in the 
fabric:

echo 1 > /sys/bus/ccw/drivers/zfcp/<bus_id>/port_rescan

This is nondisruptive.  You don't have to toggle the device off and on.

I don't have access to an SP4 system at the moment to see if any of the 
tools use port_rescan.

Regards,

Ray Higgs
System z IO Firmware Development
Bld. 706, B42
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com



From:   Mark Post <mp...@suse.com>
To:     LINUX-390@VM.MARIST.EDU
Date:   01/24/2016 06:38 PM
Subject:        Re: New LUNs on SLES 11 SP4
Sent by:        Linux on 390 Port <LINUX-390@VM.MARIST.EDU>



>>> On 1/24/2016 at 12:47 PM, Jorge Fábregas <jorge.fabre...@gmail.com> 
wrote: 
> 5) some MISSING COMMAND here to recognize these new targets

I haven't tried it myself, but perhaps the zfcp_san_disc command would be 
of use here.


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/

Reply via email to