Well it looks like something has changed since last fall. Here is the zfcp
definitions prior to patching.
# Configure zFCP device at 0.0.0400
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0400", IMPORT{program}="collect
0.0.0400 %k 0.0.0400 zfcp"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="zfcp", IMPORT{program}="collect
0.0.0400 %k 0.0.0400 zfcp"
ACTION=="add", ENV{COLLECT_0.0.0400}=="0", ATTR{[ccw/0.0.0400]online}="1"
ACTION=="add", KERNEL=="rport-*", ATTR{port_name}=="0x50000972081ca531",
SUBSYSTEMS=="ccw", KERNELS=="0.0.0400",
ATTR{[ccw/0.0.0400]0x50000972081ca531/unit_add}="0x0000000000000000"
ACTION=="add", KERNEL=="rport-*", ATTR{port_name}=="0x50000972081ca531",
SUBSYSTEMS=="ccw", KERNELS=="0.0.0400",
ATTR{[ccw/0.0.0400]0x50000972081ca531/unit_add}="0x0001000000000000"
And here after patching. Note the comment and the port and lun numbers. These
are ones we haven't used in a few years.
# Rules converted from zfcp-bus-ccw-0.0.0400
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0400", IMPORT{program}="collect
0.0.0400 %k 0.0.0400 zfcp"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="zfcp", IMPORT{program}="collect
0.0.0400 %k 0.0.0400 zfcp"
ACTION=="add", ENV{COLLECT_0.0.0400}=="0", ATTR{[ccw/0.0.0400]online}="1"
ACTION=="add", KERNEL=="rport-*", ATTR{port_name}=="0x5006048ad52f8f77",
SUBSYSTEMS=="ccw", KERNELS=="0.0.0400",
ATTR{[ccw/0.0.0400]0x5006048ad52f8f77/unit_add}="0x007f000000000000"
ACTION=="add", KERNEL=="rport-*", ATTR{port_name}=="0x5006048ad52f8f77",
SUBSYSTEMS=="ccw", KERNELS=="0.0.0400",
ATTR{[ccw/0.0.0400]0x5006048ad52f8f77/unit_add}="0x0080000000000000"
It looks like this server and another one that had the issue still have files
in /etc/sysconfig/hardware
-rw-r--r-- 1 root root 471 Jul 20 2010 hwcfg-dasd-bus-ccw-0.0.0100
-rw-r--r-- 1 root root 469 Jul 20 2010 hwcfg-dasd-bus-ccw-0.0.0300
-rw-r--r-- 1 root root 469 Jul 20 2010 hwcfg-dasd-bus-ccw-0.0.0301
-rw-r--r-- 1 root root 275 Jul 20 2010 hwcfg-qeth-bus-ccw-0.0.0600
-rw-r--r-- 1 root root 512 Feb 16 2010 hwcfg-zfcp-bus-ccw-0.0.0400
-rw-r--r-- 1 root root 512 Feb 16 2010 hwcfg-zfcp-bus-ccw-0.0.0401
-rwxr-xr-x 1 root root 7898 Jan 31 07:45 hwcfg2rules
Here is a portion of this file
# Configured zfcp disks
ZFCP_LUNS="
0x5006048ad52f8f77:0x007f000000000000
0x5006048ad52f8f77:0x0080000000000000"
None of our other servers have any of these files except for the hwcfg2rules
file.
slx111cln1:/etc/sysconfig/hardware # dir
total 8
-rwxr-xr-x 1 root root 7898 Jul 23 2012 hwcfg2rules
The only difference I can see is that potentially we created the other servers
from a clean install of sles11 (dvd) and this one was upgraded from sles10 to
sles11.
Chris Will
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Mark Post
Sent: Thursday, July 11, 2013 3:05 PM
To: [email protected]
Subject: Re: zfcp devices missing after patching
>>> On 7/11/2013 at 09:16 AM, "Will, Chris" <[email protected]> wrote:
> Now after patching and reboot, the servers come up with no LUNs
> attached (we have the root file system on eckd, but program and data files
> are on LUNs).
> If I add them back in with zfcp_disk_configure that seems to resolve
> the issue and the servers reboot with no issues. Any ideas what may
> be causing this?
The only thing I can think of is to look in /etc/udev/rules.d/ and make sure
your zfcp rules files are all there. Those are what cause the FCP adapter and
LUNs to be activated. In any case, a service request should be opened with
your support provider. That sort of a simple change shouldn't have these kinds
of consequences.
Mark Post
----------------------------------------------------------------------
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/
The information contained in this communication is highly confidential and is
intended solely for the use of the individual(s) to whom this communication is
directed. If you are not the intended recipient, you are hereby notified that
any viewing, copying, disclosure or distribution of this information is
prohibited. Please notify the sender, by electronic mail or telephone, of any
unintended receipt and delete the original message without making any copies.
Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are
nonprofit corporations and independent licensees of the Blue Cross and Blue
Shield Association.
----------------------------------------------------------------------
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/
