Back in April when I was experimenting with V-disk, I found that you don't have to bother with CMS FORMAT and RESERVE for a V-disk swap file.
mkswap writes just two records to the V-disk; so, next to no time is taken up during Linux boot. Being chicken, I also do: chmod 600 /dev/dasdb1 before the swapon. ----- Original Message ----- From: "Wolfe, Gordon W" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 11:32 AM Subject: Re: swap file alloc > You can also use V-disk for swap. This doesn't use any allocated disk, but > puts your swap into virtual storage, which means into XSTORE and paging > DASD. It requires a little setup, but is much faster than Linux DASD > swapping. > > The following example assumes you boot from the 292 disk (dasdb) and use the > 293 disk (dasda) for swap. Your /boot/parmfile should reflect this. > > In the VM Directory for the Linux server, add > MDISK 293 FB-512 V-DISK 250000 MR LINUX SWAP DASDA > > Then in the Linux Server's PROFILE EXEC, you will have to add > queue '1' > queue 'LXSWAP' > 'FORMAT 293 E ( BLK 4096' > if rc <> 0 then exit rc > queue '1' > 'RESERVE LINUX SWAP E6' > if rc <> 0 then exit rc > 'CP IPL 292 CLEAR' > > Then you have to modify the /sbin/init.d/boot file as follows: (about line > 150 in SuSE 2.2.16) > > #cho "Activating swap-devices in /etc/fstab..."#wapon -a &> /dev/nullecho "Formatting T-DISK swap partition"dasdfmt -b 4096 -y -f /dev/dasdaecho "Creating swap file signature"mkswap /dev/dasda1echo "Activating swap partition"swapon /dev/dasda1 > > Then when you IPL CMS for the Linux server, it will create a CMS RESERVED > V-disk for Linux, and then boot the 292 disk. During the Linux boot, Linux > will format the 293 for Linux and create a swap partition on it and use it. > > "Problems worthy of attack prove their worth by hitting back." > -Piet Hein, Journal of Irreproducible Results March, 1971 > Gordon W. Wolfe, Ph.D > VM Technical SErvices, The Boeing Company, (425)865-5940 > > > ---------- > > From: Post, Mark K > > Reply To: Linux on 390 Port > > Sent: Thursday, January 17, 2002 8:04 AM > > To: [EMAIL PROTECTED] > > Subject: Re: swap file alloc > > > > Jammie, > > > > You can create a swap file on one of those volumes. You won't need to > > allocate the entire volume. 48MB of storage is pretty tight. I don't > > know > > about the new SuSE install, but I ran into problems installing various > > versions of the Red Hat beta without enough RAM, even though I allocated a > > large swap partition. Hopefully that won't be an issue for you. Section > > 16.6.6 of the RedBook you cite talks about how to set up a swap file. > > > > Mark Post > > > > -----Original Message----- > > From: Hall, Jammie [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 17, 2002 10:40 AM > > To: [EMAIL PROTECTED] > > Subject: swap file alloc > > > > > > I am running the LPAR and I only have two DASD allocated for this test > > install 0187 & 0188. I read in an article that you could run without a > > swap file. Is this true? I have 48MB Memory allocated. I figure I'll run > > into problems. Can I allocate a partial drive to swap? I do not want to > > be forced to have a full 2GB allocated to swap. That is extreme I think. > > I'm install SuSE 7.3 and reading the SuSE install guide and SG24-6264-00 > > they make me believe I have to allocate the full 2GB. > > > > By the way, dasdfmt still going strong. > > > > Thanks, j-me > > > >
