Just started doing this on our z800... Neale, your presentation is a great guide. Also useful are a Redbook and Redpaper on the subject:
"Implementing Linux with IBM Disk Storage" (good information about the ESS side of the issue) "Getting Started with zSeries Fibre Channel Protocol" (more help to get the Linux side right) The disks do appear as SCSI disks. If you're not using devfs, the device nodes you need are even the same as you'd see on an Intel machine: /dev/sda etc. A couple of hints: - if you are not able to obtain a pre-prepared util-linux package (required to get fdisk), it is easy to rebuild it from the source RPM for your distro. To be neat about it, you may need to rebuild s390-utils also (I had to on Red Hat, because their s390-utils includes fdisk as a symlink to fdasd) - devfs is recommended, and I just finished configuring devfsd to allow me to add the FCP disks to /etc/fstab and have them automatically mounted at boot (without some of the scripted mechanisms in various documentation). This is using a 2.4.19 kernel on Red Hat 7.2. Cheers, Vic Cross On Wed, 28 May 2003, Don Mulvey wrote: > I was wondering if anyone could comment about accessing 5120 storage from > their Linux systems. I heard that the disks appear as scsi disks and so > the 390 dasd block driver isn't involved in accessing/formatting these > devices. In fact, my understanding is that you use the IBM Subsystem > Device Driver to access the disks, using the multipath support found in the > IBM SDD. Can anyone describe their experiences with the 5120 ... aka > shark ... and confirm/clarify how you access the disks? > > Thanks! > > Don Mulvey >
