On Mon, Aug 23, 2010 at 10:05:18PM -0400, martin roby wrote: > You right. NPIV. I am wondering , if it is an issue to not use it when > booting off a san. > > > I am from a linux san world where only cluster disks would be on > the same scsi bus. (using a cluster container) > I am not 100% sure , but it seems when the system is starting, it > runsinitrd and the modules for the devices load our system might find > other disks on the bus. > > It could be something unrelated but our san disks don't seem to work > well (stable) for holding root and swap. When booting I get a message > that it can't mount the rootfs.
When booting the Linux from a SAN disk, the scripts in the initrd should take care of configuring the LUNs to use, wait for the SCSI devices to appear and setup multipathing before trying to mount the root filesystem. Which distribution is this and how does the setup look like? > I don't see any other disks on the scsi bus when I boot the system > from a non-san drive. > > I seemed to remember a similar rootfs bug related to sub_fs and lvm, > so I realize it could be a lot of different issues, but I am > wondering it has ever been found that > the wfcp driver will probe the scsi bus at bootup if another scsi or > dm module loads. The zfcp driver right now does not probe SCSI LUNs automatically. The reason for this is that the driver has been written for non-NPIV mode initially; in this mode the operating systems sharing the FCP channel have to cooperate by only accessing the LUNs they need. NPIV support has been added while keeping the same config mechanism in place. -- Christof Schmitt ---------------------------------------------------------------------- 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/
