The HOWTO's basevol/guestvol scheme says the /boot filesystem is to be read-only and shared by all the basevol/guestvol guests. That probably won't work if each guest is to have it's own LUN(s) activated by the shared initial ramdisk on the shared boot dasd. Each LUN has a unique "address"; the initial ramdisk would have to be built to activate all the LUNs unique addresses. Might be easier to activate a guest's LUN(s) in the post-initial ramdisk phase, boot.local maybe?
-------------------------------------------------------- This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Matt Gourley Sent: Friday, May 04, 2007 2:51 PM To: [email protected] Subject: Re: Basevol/Guestvol and ZFCP Mark Post wrote: >>>> On Fri, May 4, 2007 at 2:00 PM, in message <[EMAIL PROTECTED]>, Matt >>>> > Gourley <[EMAIL PROTECTED]> wrote: > -snip- > >> 2) If I add the LUN to the guestvol system through YaST and reboot, the >> LUN information is lost. Obviously, this isn't good. :) >> > -snip- > > Sounds like you need to re-run mkinitrd and zipl. > There's where I'm running into issues. I can't run mkinitrd and zipl from the guestvol system, as it's seeing /sys and /boot as read-only. I have added the following line to /etc/sysconfig/kernel on the basevol: INITRD_MODULES="dasd_fba_mod zfcp" and have run mkinitrd and zipl on the basevol. Without this, I would not have been able to see the LUN. When we setup the DASD beyond the 202 disk on the other guests, we had a similar problem. The solution was to write a script to mount any ext[23] filesystem in /etc/fstab that wasn't already mounted or /guestvol, and put that in /etc/init.d/rc3.d between the system scripts and the application scripts. -Matt -- Matt Gourley Systems Administrator Pennsylvania State University Administrative Information Services - Infrastructure/Sysarc Rm 25 Shields Bldg., University Park, PA 16802 (814) 865-8726 [EMAIL PROTECTED] ---------------------------------------------------------------------- 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 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
