Ok, so after the swap is created in z/VM and formatted using SWAPGEN, I see the devices in Linux. However, I still have to issue the mkswap and swapon commands to activate them.
I added these commands to boot.swap under start): modprobe dasd_fba_mod echo "Creating swap file signature..." mkswap /dev/dasdg1 mkswap /dev/dasdh1 Looking at /var/log/boot.msg, I see: Creating swap file signature... /dev/dasdg1: No such device or address /dev/dasdh1: No such device or address After the machine is up, I can run mkswap and swapon. -Channon -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, October 16, 2007 4:37 PM To: [email protected] Subject: Re: Expanding SWAP space >>> On Tue, Oct 16, 2007 at 5:31 PM, in message <[EMAIL PROTECTED]>, "Quillen, Channon" <[EMAIL PROTECTED]> wrote: > They are VDISK for swap. All the other drives are ECKD. Is there any > benefit to having them one way or the other? They both seemed to be on the small side for swap, so I thought I'd better ask. No, don't change them to ECKD unless you want to seriously damage your Linux paging performance. If I were you, I would use Sine Nomine's SWAPGEN exec to prepare them, though. They should be showing up as DIAG, not FBA, which will also provide a performance benefit. Mark Post ---------------------------------------------------------------------- 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
