Hi, Try running mkinitrd with --with=zfcp. It forces mkinitrd to include the new version of /etc/zfcp.conf in the new initrd.
And just for completeness, make sure to run zipl afterwards, otherwise the old LUNs will appear along with the new ones - the old ones come from the initrd and the new ones come from /etc/zipl.conf. Now that I think about it, that's more likely the issue. Could the zipl step be missing? -- Brad Hinson <[email protected]> Worldwide System z Sales, Strategy, Marketing Red Hat, Inc. +1 (919) 360-0443 http://www.redhat.com/z On Feb 29, 2012, at 6:44 AM, Offer Baruch wrote: > Sorry... I forgot to mention that rebuilding the initrd did not help. I am > running with rhel v5 > On 29 בפבר 2012 13:41, "Steffen Maier" <[email protected]> wrote: > >> On 02/29/2012 07:07 AM, Offer Baruch wrote: >> >>> I have a strange zfcp problem i just can't figure out... >>> My OS runs on ECKD but i have a few luns on an XIV machine for oracle >>> data. >>> We are in the middle of a migration process from one XIV to another. >>> my /etc/zfcp.conf used to look like this (before the migration): >>> # >>> 0.0.0010 0x0 0x5001738000800140 0x0 0x0000000000000000 >>> 0.0.0010 0x0 0x5001738000800150 0x0 0x0000000000000000 >>> 0.0.0010 0x0 0x5001738000800160 0x0 0x0000000000000000 >>> 0.0.0011 0x0 0x5001738000800171 0x0 0x0000000000000000 >>> 0.0.0011 0x0 0x5001738000800181 0x0 0x0000000000000000 >>> 0.0.0011 0x0 0x5001738000800191 0x0 0x0000000000000000 >>> >> >> and now it looks like this (different WWPNs and i got rid of lun zero): >>> # >>> 0.0.0011 0x0 0x5001738062670140 0x0 0x0001000000000000 >>> 0.0.0011 0x0 0x5001738062670150 0x0 0x0001000000000000 >>> 0.0.0011 0x0 0x5001738062670160 0x0 0x0001000000000000 >>> 0.0.0010 0x0 0x5001738062670170 0x0 0x0001000000000000 >>> 0.0.0010 0x0 0x5001738062670180 0x0 0x0001000000000000 >>> 0.0.0010 0x0 0x5001738062670190 0x0 0x0001000000000000 >>> >> >> I expected that after a reboot zfcp will forget about the old luns but he >>> didn't. >>> looking at: >>> /sys/bus/ccw/drivers/zfcp/0.0.**0010 >>> /sys/bus/ccw/drivers/zfcp/0.0.**0011 >>> i can still see the old ports and luns. for example: >>> drwxr-xr-x 6 root root 0 Feb 28 15:17 0x5001738000800140 - old >>> drwxr-xr-x 6 root root 0 Feb 28 15:17 0x5001738000800150 - old >>> drwxr-xr-x 6 root root 0 Feb 28 15:17 0x5001738000800160 - old >>> drwxr-xr-x 5 root root 0 Feb 28 15:17 0x5001738062670170 -new >>> drwxr-xr-x 5 root root 0 Feb 28 15:17 0x5001738062670180 -new >>> drwxr-xr-x 5 root root 0 Feb 28 15:17 0x5001738062670190 -new >>> under 0x5001738000800140 you can see the old luns: >>> drwxr-xr-x 2 root root 0 Feb 28 15:17 0x0000000000000000 >>> drwxr-xr-x 2 root root 0 Feb 28 15:17 0x0001000000000000 >>> drwxr-xr-x 2 root root 0 Feb 28 15:17 0x0002000000000000 >>> drwxr-xr-x 2 root root 0 Feb 28 15:17 0x0003000000000000 >>> >>> something does not add up. i guess i have some misunderstanding about zfcp >>> start up procedure. >>> I though the script zfcpconf.sh is run at startup using the >>> 56-zfcp.rules* *udev >>> rule and that is it... >>> as all 56-zfcp.rules* *does is run zfcpconf.sh i can't figure out where >>> did >>> the system get the old luns/ports? >>> >> >> I suppose this is RHEL 5: You may need to regenerate your initrd after >> modifications to /etc/zfcp.conf since this gets added to the initrd, IIRC. >> On reboot, your old initrd containing the old zfcp.conf still activates the >> old WWPNs and LUNs before the root-fs gets mounted. >> >> (All this differs for RHEL 5, RHEL 6, SLES 10, SLES 11.) >> >> zfcpconf.sh just reads /etc/zfcp.conf >>> >> >> That adds the new WWPNs and LUNs after the root-fs was mounted. >> >> HTH >> Steffen >> >> Linux on System z Development >> >> IBM Deutschland Research & Development GmbH >> Vorsitzende des Aufsichtsrats: Martina Koederitz >> Geschäftsführung: Dirk Wittkopp >> Sitz der Gesellschaft: Böblingen >> 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<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/ ---------------------------------------------------------------------- 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/
