I looked at line number 51 and I don't understand why it failing on
that...that's essentially how I was adding the luns (or so I thought).
Device 0.0.4100
# ls -la /sys/bus/ccw/drivers/zfcp/0.0.4100
lrwxrwxrwx. 1 root root 0 Jul 16 11:40 /sys/bus/ccw/drivers/zfcp/0.0.4100
-> ../../../../devices/css0/0.0.0003/0.0.4100
# ls -la /sys/bus/ccw/drivers/zfcp/0.0.4100/0x500507630900c620
drwxr-xr-x. 3 root root 0 Jul 16 11:40 .
drwxr-xr-x. 5 root root 0 Jul 16 11:40 ..
-r--r--r--. 1 root root 4096 Jul 16 11:41 access_denied
-rw-r--r--. 1 root root 4096 Jul 16 11:41 failed
-r--r--r--. 1 root root 4096 Jul 16 11:41 in_recovery
drwxr-xr-x. 2 root root 0 Jul 16 11:41 power
-r--r--r--. 1 root root 4096 Jul 16 11:41 status
-rw-r--r--. 1 root root 4096 Jul 16 11:41 uevent
--w-------. 1 root root 4096 Jul 16 11:40 unit_add
--w-------. 1 root root 4096 Jul 16 11:41 unit_remove
Device 0.0.4200
# ls -la /sys/bus/ccw/drivers/zfcp/0.0.4200
lrwxrwxrwx. 1 root root 0 Jul 16 11:40 /sys/bus/ccw/drivers/zfcp/0.0.4200
-> ../../../../devices/css0/0.0.0004/0.0.4200
The below initially failed when using the WWPN 0x500507630900c620 instead
of what I think it should be used0x50050763090bc620.
# ls -la /sys/bus/ccw/drivers/zfcp/0.0.4200/0x50050763090bc620
drwxr-xr-x. 3 root root 0 Jul 16 11:40 .
drwxr-xr-x. 5 root root 0 Jul 16 11:40 ..
-r--r--r--. 1 root root 4096 Jul 16 11:43 access_denied
-rw-r--r--. 1 root root 4096 Jul 16 11:43 failed
-r--r--r--. 1 root root 4096 Jul 16 11:43 in_recovery
drwxr-xr-x. 2 root root 0 Jul 16 11:43 power
-r--r--r--. 1 root root 4096 Jul 16 11:43 status
-rw-r--r--. 1 root root 4096 Jul 16 11:43 uevent
--w-------. 1 root root 4096 Jul 16 11:40 unit_add
--w-------. 1 root root 4096 Jul 16 11:43 unit_remove
This is how I am dynamically allocating the luns:
echo 0x4009400000000000 >
/sys/bus/ccw/drivers/zfcp/0.0.4100/0x500507630900c620/unit_add
0x50050763090bc620
Jason Space
zVM|zOS 3rd Party Software
Mainframe Services Branch
Division of Platform Services
Information and Security Services
Bureau of the Fiscal Service
jason.sp...@fiscal.treasury.gov
304.480.6733
The contents of this message are mine personally and do not reflect any
position of the Government or my agency. Use of this equipment is
consistent with the agency’s policy governing limited personal use.
From: Grzegorz Powiedziuk <gpowiedz...@gmail.com>
To: LINUX-390@VM.MARIST.EDU,
Date: 07/16/2015 11:23 AM
Subject: Re: zFCP LUNs Not Persistent Across Reboot (RHEL 6.6)
Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
ok line 51 is :
echo $FCPLUN > /sys/bus/ccw/drivers/zfcp/${DEVICE}/${WWPN}/unit_add
So now do
ls -la /sys/bus/ccw/drivers/zfcp/0.0.4200/
and
ls -la /sys/bus/ccw/drivers/zfcp/0.0.4200/0x500507630900c620/
The second one probably will fail
How are you adding these luns dynamically?
Gregory Powiedziuk
2015-07-16 11:07 GMT-04:00 Jason Space <jason.sp...@fiscal.treasury.gov>:
> I tried that yesterday also, but i get the following message over and
over
> - assuming it is for each lun that is tried to bring online:
> /sbin/zfcpconf.sh: line 51: echo: write error: Invalid argument
>
>
>
>
>
> From: Grzegorz Powiedziuk <gpowiedz...@gmail.com>
> To: LINUX-390@VM.MARIST.EDU,
> Date: 07/16/2015 10:55 AM
> Subject: Re: zFCP LUNs Not Persistent Across Reboot (RHEL 6.6)
> Sent by: Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
>
>
>
> after the boot, when you are missing luns, what would happen if you just
> run
> /sbin/zfcpconf.sh
>
> Would these luns show up?
>
> Gregory Powiedziuk
>
> 2015-07-16 7:42 GMT-04:00 Offer Baruch <offerbar...@gmail.com>:
>
> > Hi...
> >
> > Try having a look at this rhel 6 defect.
> > https://bugzilla.redhat.com/show_bug.cgi?id=957847
> > Try and update you udev rule and see if that give you any better
> results...
> >
> > Offer Baruch
> > On Jul 16, 2015 1:44 PM, "Jason Space"
<jason.sp...@fiscal.treasury.gov>
> > wrote:
> >
> > > All,
> > >
> > > I'm having trouble getting luns to be persistent across a reboot of
> linux
> > > guest. I am able to define the luns dynamically, just not get them
to
> > > stick.
> > >
> > > On boot messages log show:
> > > scsi0 : zfcp
> > > qdio: 0.0.4100 ZFCP on SC 3 using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W
AO
> > > scsi1 : zfcp
> > > qdio: 0.0.4200 ZFCP on SC 4 using AI:1 QEBSM:1 PCI:1 TDD:1 SIGA: W
AO
> > >
> > >
> > > Output of the lszfcp:
> > > # lzfcp -PHD
> > > 0.0.4100 host0
> > > 0.0.4200 host1
> > > 0.0.4100/0x500507630900c620 rport-0:0-0
> > > 0.0.4200/0x50050763090bc620 rport-1:0-0
> > > Error: No fcp devices found.
> > >
> > > Output of the lsluns (snippet)
> > > # lsluns
> > > Scanning for LUNs on adapter 0.0.4100
> > > at port 0x500507630900c620:
> > > 0x4009400000000000
> > > 0x4009400100000000
> > > 0x4009400200000000
> > > .
> > > .
> > > Scanning for LUNs on adapter 0.0.4200
> > > at port 0x50050763090bc620:
> > > 0x4009400000000000
> > > 0x4009400100000000
> > > 0x4009400200000000
> > >
> > > Per RHEL manual, I have created the /etc/zfcp.conf (snippet) file
with
> > all
> > > the required information:
> > > 0.0.4100 0x500507630900c620 0x4009400000000000
> > > 0.0.4100 0x500507630900c620 0x4009400100000000
> > > 0.0.4100 0x500507630900c620 0x4009400200000000
> > > .
> > > .
> > > 0.0.4200 0x50050763090bc620 0x4009400000000000
> > > 0.0.4200 0x50050763090bc620 0x4009400100000000
> > > 0.0.4200 0x50050763090bc620 0x4009400200000000
> > >
> > > Also found a RHEL support case saying to create a
> > > /etc/modprobe.d/zfcp.conf for non-root luns, but that didn't work
> either.
> > > alias scsi_hostadapter zfcp
> > >
> > >
> > > Thx,
> > > Jason
> > >
> > >
----------------------------------------------------------------------
> > > 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/
> >
>
> ----------------------------------------------------------------------
> 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/
>
----------------------------------------------------------------------
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/
