Thanks Adam.. That makes total sense. BTW as I was messing around I see I do have dasd_diag_mod, so I guess I could use the 'perfered' DIAG format in SWAPGEN and then swap to dasdb1 ..
This LINUX stuff is going to make the rest of my hair turn grey.. -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Adam Thornton Sent: Thursday, July 31, 2008 4:30 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: VDISK-SWAP-SWAPGEN ??? On Jul 31, 2008, at 3:59 PM, Huegel, Thomas wrote: > Yes I have dasd_fba_mod loaded, I don't know about dasd_diag_mod.. > > Here are some more messages... > > swapon -a > Unable to find swap-space signature > swapon: /dev/dasdb1: Invalid argument > linmstr:~ # Jul 31 15:54:23 linmstr kernel: Unable to find swap- > space signature > swapon /dev/dasdb > swapon /dev/dasdb > Adding 49992k swap on /dev/dasdb. Priority:-1 extents:1 > Jul 31 15:55:19 linmstr kernel: Adding 49992k swap on /dev/dasdb. > Priority:-1 extents:1 Hmmm, OK. So the swapspace signature IS on /dev/dasdb, and it swapped on OK. So I think what's going on is that, for some reason, it's initially trying to swap on before dasd_fba_mod is loaded. So you probably need to build the ramdisk again with dasd_fba_mod in it, or you can just do a late-in-the-boot-process swapon -a once the device driver is loaded. Adam ---------------------------------------------------------------------- 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
