On 19.03.2003 at 09:06:12, Jeremy Warren <[EMAIL PROTECTED]> wrote: > MDISK 9000 FB-512 V-DISK 262144 MR ALL SOME FEW * 128MB SWAP FILE
Looks OK, except do you really want to provide multiple access to the disk? Sharing swap is a big no-no; personally I'd not include those passwords. > 'FORMAT 9000 E ( BLK 4096' Not sure you should change the blocksize... FBA devices are natively 512B blocked, and I'm pretty sure the FBA discipline of the DASD driver knows this. <snip> > So then if I do: > insmod dasd_fba_mod > > Then do a swapon /dev/dasda I get: > swapon: /dev/dasda: Invalid argument Yep. > But if after the insmod I do a mkswap and a swapon at this point it works. Yep. ;-) > I know my issue with the "No such device" is the fba module isn't being > loaded (part2) but as far as part 1 goes, I "thought" (always dangerous > words) that the QUEUE 1 LXSWAP stuff in the profile exec was seeding the > swap disk so I didn't have to do a mkswap during boot and all I needed to > do was add a swapon line to the boot.local. The code you have in your PROFILE EXEC does a CMS format of the disk, followed by a CMS RESERVE (the QUEUE commands prepare the input for the FORMAT and RESERVE commands, since these are interactive). This process does not put any information on the disk (other than CMS formatting), and certainly doesn't put a swap signature on it. To get CMS to prepare the disk for you, you would need to find out what parts of the swap device comprise the swap signature, copy them out to a CMS file, and then get your PROFILE EXEC to copy that swap signature back onto the swap device after formatting. A different approach would be to find the point in your rc.sysinit script where the swapon command is issued, and issue appropriate mkswap commands. Cheers, Vic Cross
