This is exactly what I needed. Thank you. The VDISK swap procedure follows correctly from that point forward.
John -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Wednesday, July 18, 2007 12:27 PM To: [email protected] Subject: Re: RedHat ES 4 using VDISK Do you see the disk in the output of 'lsdasd'? If not (which is likely), you will need to rebuild the initrd. This is a little different from SLES, where I believe you append it in zipl.conf. For RHEL, modify the "dasd=" line in /etc/modprobe.conf, then run: # cp /boot/initrd-`uname -r`.img /boot/initrd-`uname -r`.img.backup # mkinitrd -v -f /boot/initrd-`uname -r`.img `uname -r` In the output, you should see: [snip] Adding module dasd_mod with options dasd=xxx,xxx,302 [..] Then run /sbin/zipl to update the changes. After a reboot (or bringing it online manually), /sbin/lsdad should show something like: 0.0.0302(FBA ) at ( 94: 24) is dasdx : active at blocksize 512, 524288 blocks, 256 MB -Brad On Wed, 2007-07-18 at 11:47 -0400, Beth Somers wrote: > Nevermind, I saw the posts, I just did not scroll down far enough. > Wew, OK, you will get alot of crap, but hopefully someone from RedHat will bite. > Anyway, we will figure this out. Have a nice vacation and we will work > on it when you get back (oh yeah, I am off next week so perhaps the > week after). Beth > > Beth Somers > Certified Consulting I/T Specialist - Large and Storage Systems > [EMAIL PROTECTED] > 813-334-1238 > > > > > John White > <[EMAIL PROTECTED] > m> To > Sent by: Linux on [email protected] > 390 Port cc > <[EMAIL PROTECTED] > IST.EDU> Subject > Re: RedHat ES 4 using VDISK > > 07/18/2007 11:00 > AM > > > Please respond to > Linux on 390 Port > <[EMAIL PROTECTED] > IST.EDU> > > > > > > > The following is the contents of our /etc/zipl.conf. > > [EMAIL PROTECTED] network-scripts]# cat /etc/zipl.conf [defaultboot] > default=linux target=/boot/ [linux] > image=/boot/vmlinuz-2.6.9-55.EL > ramdisk=/boot/initrd-2.6.9-55.EL.img > parameters="root=LABEL=/" > > According to (http://www.linuxvm.com/vdskdoit.html) We're supposed to > add the disk to the Linux Boot Parameter file, 'i.e. disk=302' in our > case. I added it as, "parameters="root=LABEL=/ disk=302" and it did > not make a difference. When I do a listing of /dev/dasd* there does > not show a corresponding device to run a 'mkswap' or 'mke2fs' command > against. > > The 302 disk is CMS FORMAT'ted. > > John > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Rick Troth > Sent: Wednesday, July 18, 2007 5:37 AM > To: [email protected] > Subject: Re: RedHat ES 4 using VDISK > > On Wed, 18 Jul 2007, Srinivasa R Chamarthy wrote: > > Can you let me know what is your /etc/zipl.conf ? And also let me > > know > > > if you are using a CMS formatted disk. If it is a CMS formatted disk > > then you can not put swap to it. and also give me the output for > > lsdasd. It would help me in debugging. > > Not exactly. > > Just for clarification, > CMS FORMAT does two things: low-level format (akin to 'dasdfmt') and > high-level format (akin to 'mke2fs'). If the disk is FBA or VDSK then > CMS FORMAT silently skips the low-level formatting operation. > > In general, FBA and VDSK should be usable immediately without CMS > FORMAT (and without 'dasdfmt'). You can simply 'mkswap' > or 'mke2fs' and use the whole disk. If you need partitioning, the > story changes. And if you use 'dasdfmt -l cdl' the waters get even > murkier w/r/t using "the whole disk". > > But the low-level half of the CMS FORMAT operation is essential prior > to using CKD disks, unless one runs 'dasdfmt' in Linux. > > *** summary *** > > CKD or ECKD -- require low-level formatting > > FBA, VDSK, SAN -- do not require low-level formatting > > CMS FORMAT -- performs low-level and high-level > formatting > > 'mkswap' -- performs high-level formatting for swap space and > can be run even if the disk was CMS FORMATted > > 'mke2fs' -- performs high-level formatting for a > filesystem and > can be run even if the disk was CMS FORMATted > > Partitioning schemes may throw-off the latter two. > > -- R; > > ---------------------------------------------------------------------- > 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 > > ---------------------------------------------------------------------- > 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 -- Brad Hinson <[EMAIL PROTECTED]> Red Hat, Inc. (888) 733-4281 x44198 ---------------------------------------------------------------------- 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
