Okay first, I had already changed my 
/etc/sysconfig/hardware/config-ccw-0.0.a200 to the way that you suggested based 
on a recommendation from David Straub.

So on to the "lszfcp" commands. Before and after reboot are the same for 
"lszfcp -HV" command
        # lszfcp -HV
        /sys/devices/css0/0.0.0006/0.0.a200
        /sys/class/fc_host/host0
        /sys/class/scsi_host/host0
        /sys/devices/css0/0.0.0007/0.0.a300
        /sys/class/fc_host/host1
        /sys/class/scsi_host/host1

But the "# lszfcp -DV" command shows *nothing* after reboot and shows this 
before the reboot,
        # lszfcp -DV
        
/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035ee/0x001f000000000000
        
/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-0/target0:0:0/0:0:0:31
        /sys/block/sda /sys/class/scsi_generic/sg0
        
/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035ee/0x001f000000000000
        
/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-0/target1:0:0/1:0:0:31
        /sys/block/sdc /sys/class/scsi_generic/sg2
        
/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035ee/0x0020000000000000
        
/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-0/target0:0:0/0:0:0:32
        /sys/block/sde /sys/class/scsi_generic/sg4
        
/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035ee/0x0020000000000000
        
/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-0/target1:0:0/1:0:0:32
        /sys/block/sdg /sys/class/scsi_generic/sg6
        
/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035d9/0x001f000000000000
        
/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-1/target0:0:1/0:0:1:31
        /sys/block/sdb /sys/class/scsi_generic/sg1
        
/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035d9/0x001f000000000000
        
/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-1/target1:0:1/1:0:1:31
        /sys/block/sdd /sys/class/scsi_generic/sg3
        
/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035d9/0x0020000000000000
        
/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-1/target0:0:1/0:0:1:32
        /sys/block/sdf /sys/class/scsi_generic/sg5
        
/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035d9/0x0020000000000000
        
/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-1/target1:0:1/1:0:1:32
        /sys/block/sdh /sys/class/scsi_generic/sg7

Obviously, that is an issue. So what do you think that I'm missing? It still 
seems that I'm missing a configuration file, maybe it's not 
/etc/sysconfig/hardware/config-ccw-0.0.a200 in Debian??? I've read through 
IBM's "Device Drivers, Features, and Commands" (amongst a hundred other 
documents), but haven't found anything there either. It shows you how to 
configure the devices (echo 0x001f000000000000 > 
0.0.a200/0x50050768011035d9/unit_add) but doesn't suggest where to put those 
configuration parameters to make them permanent. I'm grateful for any help that 
you can provide.


-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Steffen 
Maier
Sent: Wednesday, October 06, 2010 5:15 PM
To: [email protected]
Subject: Re: Question about multipathing on zDebian (Lenny)

On 10/05/2010 07:35 PM, Wiggins, Mark wrote:
> I'm trying to
> add some multipath'd devices to a Debian(Lenny)  instance. I can get
> the devices configured properly,

> I just can't get these definitions to hold across a reboot. I've

In order to narrow down which activation step does not work correctly,=20
it would be interesting to know if the following holds true after the=20
boot process finished:
- zfcp adapters for each path are online
   # lszfcp -HV
- all fcp luns for each path and disk are online
   # lszfcp -DV
Those would be the prerequisites to have the necessary SCSI disks for=20
device-mapper multipath to work with. After that, dm-mp might have=20
problems. However, I'm not particular familiar with that and its config=20
file (incl. blacklists/whitelists).

> My /etc/sysconfig/hardware/config-ccw-0.0.a200 looks like this,
> # Configured zfcp disks
> ZFCP_LUNS=3D"0x50050768014035ee:0x001f000000000000"
> ZFCP_LUNS=3D"0x50050768014035d9:0x001f000000000000"
> ZFCP_LUNS=3D"0x50050768014035ee:0x0020000000000000"
> ZFCP_LUNS=3D"0x50050768014035d9:0x0020000000000000"

This seems to overwrite the ZFCP_LUNS shell variable three times and the =

last one will win. So I guess only the FCP LUN 0x0020000000000000 on=20
WWPN 0x50050768014035d9 will be set online and you're missing the other=20
three LUNs (or at least the second path to the same LUN).

This looks very much like the SLES syntax and IIRC, you have to use one=20
ZFCP_LUNS variable assignment and put each WWPN:LUN pair on a separate=20
line within the same double quotes on the right hand side of the=20
assigment, i.e.:

# Configured zfcp disks
ZFCP_LUNS=3D"0x50050768014035ee:0x001f000000000000
0x50050768014035d9:0x001f000000000000
0x50050768014035ee:0x0020000000000000
0x50050768014035d9:0x0020000000000000"

You could try tracing the hwup (shell script) command to see where it fai=
ls.
# /bin/bash -x `which hwup ...`

Not sure how debain handles disks that are members of the root-fs and=20
those that are not. If the luns are not required for the root-fs you=20
might even get away without updating the initramfs and without running=20
zipl. However, it's safe to do both steps anyway.

HTH
Steffen

Linux on System z Development

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martin Jetter
Gesch=E4ftsf=FChrung: Dirk Wittkopp
Sitz der Gesellschaft: B=F6blingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

----------------------------------------------------------------------
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/

----------------------------------------------------------------------
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/

Reply via email to