Description of problem: Upgrade from up-to-date core-1 does not find existing swap. Version-Release number of selected component: 9.90-5 How reproducible: unknown, one-out-of-one tries Steps to Reproduce: 1. install FC1 on P3 with 128MBram, 40GBHD, default partioning 2. update to latest FC1 3. install FC1.90 from CD Actual results: 256MB swap incorrectly detected as 0 swap, asks about adding a swapfile. Expected results: existing swap should have been detected and used Additional info: workaround of adding a swapfile works, leaving 512MB swap on final system instead of the proper 256MB swap.
This works for me -- can you attach your /etc/fstab?
Here is my fstab after upgrade from FC1 to FC2T1: [john@maddee john]$ cat /etc/fstab LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hda5 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0 /SWAP swap swap defaults 0 0 The swappartition was pre-existing from FC1, and the /SWAP file was added by the FC2T1 installation to work around the undetected swap.
Hmmm... can you try with the development tree and just get to the stage where it asks about the boot loader (which would be after swap detection) after commenting out the swap file from /etc/fstab? It's possible something changed although I have no clue what :/
I'm seeing the same thing, upgrading from FC1 to FC2t2. Likewise, my /etc/fstab shows both the swap partition (hda3 in my case) and the /SWAP file. Also, while the installer is running, if I use Ctrl-Alt-F2 to get to the VC running bash, and "cat /proc/swaps", I find that both are currently mounted and in use. However, the installer didn't give me the option of just reusing the existing swap partition, but wanted to create the swap file. More specifically, I'm now rerunning the installer to upgrade to FC2t2 a second time, since it crashed last time due to lack of free space (a situation that was made worse, I'm sure, by the addition of the /SWAP file from the first upgrade). When running the installer the second time, I told it not to create a swap file, but found that by the time it got to the actual package upgrades, both the existing swap partition and /SWAP file were being used in the VM pool.
This should be fixed now.