Hello All,
I tried below step as well to diagnose this issue.
[root@linux12 0.0.260c]# cd /sys/bus/ccw/drivers/zfcp/
[root@linux12 zfcp]# ls
0.0.260c 0.0.271c bind module uevent unbind
[root@linux12 zfcp]# cd 0.0.260c
[root@linux12 0.0.260c]# ls
availability cmb_enable cutype devtype driver modalias online power
subsystem uevent
[root@linux12 0.0.260c]# cat online
0
[root@linux12 0.0.260c]# cat online
0
[root@linux12 0.0.260c]# echo 1 > online
[root@linux12 0.0.260c]# cat online
1
[root@linux12 0.0.260c]# lsscsi
[root@linux12 0.0.260c]# ls -F
0x500507630710c4df/ card_version cutype driver@ hardware_version
in_recovery modalias peer_d_id peer_wwpn port_rescan status
uevent
availability cmb_enable devtype failed host0/
lic_version online peer_wwnn port_remove power/ subsystem@
[root@linux12 0.0.260c]# cd 0x500507630710c4df
[root@linux12 0x500507630710c4df]# ls -F
access_denied failed in_recovery power/ status uevent unit_add
unit_remove
[root@linux12 0x500507630710c4df]# cio_ignore -r 260c
[root@linux12 0x500507630710c4df]# chccwdev -e 260c
WARNING: Device[0.0.260c] is already online
Done
[root@linux12 0x500507630710c4df]# lszfcp -P
0.0.260c/0x500507630710c4df rport-0:0-0
[root@linux12 0x500507630710c4df]# lsscsi
[root@linux12 0x500507630710c4df]# lsluns
-bash: /sbin/lsluns: /usr/bin/perl: bad interpreter: No such file or
directory
[root@linux12 0x500507630710c4df]# cat /etc/zfcp.conf
cat: /etc/zfcp.conf: No such file or directory
But After this I couldn't able to progress , as I don't know much about the
way of solving this issue. Can anybody help.
On Wed, Nov 5, 2014 at 5:15 AM, Malcolm Beattie <beatt...@uk.ibm.com> wrote:
> 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 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/
