http://bugzilla.opensuse.org/show_bug.cgi?id=936964
http://bugzilla.opensuse.org/show_bug.cgi?id=936964#c2
--- Comment #2 from Felix Miata
you also could/want use your swap for suspend to disk, right?
All my TW installations are used exclusively for testing. I have 0 laptops. All my installations are in multiboot. Consequently, I never ever suspend.
Hm, for me, the right way looks like in above steps:
To reproduce on TW 20150630 already installed: 1-change UUID... 2-change fstab ... 3-try to boot ...
Number 2.5 is missing: call dracut to update the swap uuid inside the initrd. Ok, but this can be difficult up to impossible.
I agree about the difficult part. At least in theory, one could chroot in from whatever was booted to perform rebuild, but that would be far inferior to life as it previously existed, a herculean task if all 10, 20, 30 or more installations' initrds behaved like TW current.
Not sure what could change the UUID
1-Some distro installers insist on using and reformatting every existing swap partition found (maybe most do?). 2-delete to recreate at increased size rather than direct resize (is resize of swap even possible?). 3-decide swap is not wanted or wanted on a different disk, so remove entry from fstab, and repurpose its partition 4-scenario from recent days (in less than full detail): A: run short on / freespace with an upgrade process downloading everything in advance of installing B: reboot something else C: swapoff -a D: mkfs on "swap" partition E: (move /var from shortspaced part to former swapper part; edit its fstab accordingly) F: boot shortspaced installation and finish upgrade G: reboot something else to undo step E: H: recreate swap
IMO best and relative easy solution for now would be something like discussed on the initramfs mailing list: "Allow boot to continue if swap devices are not detected."
Seems sensible to me. Does need for swap ever begin before any login or normal autostart server operations occur?
I try to come up with something, but it may take some days.
Thanks. -- You are receiving this mail because: You are on the CC list for the bug.