Hi Robert, I'd recommend the following documentation describing the syntax of /etc/zfcp.conf, some open issue with its syntax, and what to execute to prepare for e.g. next reboot after having added new disks via FCP.
IBM Redbook (especially Section 7.3) Fibre Channel Protocol for Linux and z/VM on IBM System z, SG24-7266-00 http://publib-b.boulder.ibm.com/abstracts/sg247266.html Redhat Bugzilla 251719 - zfcpconf.sh should support 3 fields in zfcp.conf https://bugzilla.redhat.com/show_bug.cgi?id=251719 more general, distribution independent documentation: developerWorks, Linux on System z, Development stream - Documentation How to use FC-attached SCSI devices with Linux on System z, SC33-8413-00 http://download.boulder.ibm.com/ibmdl/pub/software/dw/linux390/docu/l26dts00.pdf Kind regards Steffen Maier Linux on System z Development IBM Deutschland Research & Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Erich Baier Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 Linux on 390 Port <[email protected]> wrote on 08/13/2008 10:48:11 PM: > We¹re finally getting back around to ³playing² with zFCP, and I¹ve run into > a possible bug.... > > We¹re able to get things up and running by hand, and we¹re now trying to set > things up to happen during the boot of the system. Everything points back > around to a file called /etc/zfcp.conf, but there¹s very little on what¹s > really required in the file (i.e. What the five fields really mean / where > to go to get the information to fill them out). I think we¹ve figured them > out, but it would have been more reassuring to have found some detailed > documentation. Or maybe even a man page? > > Also, there¹s a script called /sbin/zfcpconf.sh, that appears to be entirely > wrong. It lops the 0x off the front of the device address, and uses it in > the /sys directory path, but fails to add the ³0.0.² to the front of it. > Could it have ever worked? I¹m not sure I see how... Adding in the ³0.0.² > into the paths used in the script seems to make it work correctly. > > The second question is, does this script actually get envoked during the > boot? Or do we have to slip it in somewhere in the /etc/init.d path? > > -- > Robert P. Nix Mayo Foundation .~. > RO-OE-5-55 200 First Street SW /V\ > 507-284-0844 Rochester, MN 55905 /( )\ > ----- ^^-^^ ---------------------------------------------------------------------- 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
