On 10/20/2013 01:11 PM, Chris Murphy wrote:
On Oct 20, 2013, at 4:38 AM, Gene Czarcinski <gene@xxxxxxxxx> wrote:
Before 20.25.1, if you had an existing swap on a regular partition or a logical volume and you specified --noformat, that swap specification was added to fstab. With 20.25.1, this is no longer the case and you wind up with no swap at all. You might want to not reformat that swap because you are using UUID and you have another system (multiboot) also using that swap and refering to it also by UUID. This problem is reported by:
https://bugzilla.redhat.com/show_bug.cgi?id=1020867
Again, I have attached a tested patch to correct the problem to the bugzilla report.
This swap problem was introduced by changes made in 20.25.1.
It might be related to this:
http://www.freedesktop.org/software/systemd/man/systemd-gpt-auto-generator.html
Since systemd is auto mounting certain partitiontypeguids, they don't need to be in fstab. There are few bugs filed as a result of the ensuing confusion. So it might be new behavior in anaconda 20.25.1 to ignore the request to reuse existing swap by adding it to fstab since it knows systemd is going to use it in any case.
If I specifically specify an existing regular partition or logical
volume as swap and specify "--noformat" in the kickstart file, then the
way it has been working is that such swap specifications are added to fstab.
Currently, a bigger aggravation to me is that if I am just doing a
install using the GUI, I cannot re-use an existing swap without
reclaiming the space and thus reformatting it and having it get a new
UUID. Of course if I have another system install into different
partitions and it is also using that swap by UUID, it now will be
screwed. Sometimes using UUID is not a good idea. This problem has
been bugzill'ed. I was hoping the "swap-fix" would help with that but I
believe it will not.
Gene
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
