Bug 166369
Summary: | mkinitrd assumes first swap entry in /etc/fstab is swsusp device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | mkinitrd | Assignee: | Peter Jones <pjones> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | hdegoede, skr |
Target Milestone: | --- | Keywords: | FutureFeature, Reopened |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-01-12 15:32:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2005-08-19 20:06:05 UTC
swsusp is only able to use one swap device. IIRC, it uses the one specified in resume=, regardless of the order swapon'ed. Since it doesn't look like there's any chance of upstream adding support for multiple swap devices in the near future, I'd have to suggest using a suspend2 enabled kernel. It has support for all of the things you're after. This bug report is about mkinitrd not recording the primary swap device in initrd. I don't see how it relates with the comment of adding multiple swap devices or the order of swapon. The problem is that, given: LABEL=SWAPsecondary swap swap pri=0 0 0 LABEL=SWAPprimary swap swap pri=1 0 0 it will record SWAPsecondary as the primary swap, just because it's listed first, and then resume will fail to recover the state saved in SWAPprimary. Sorry. I was concentrating too much on what you said about swsusp, not the title of the bug. So can anyone tell us when there is no resume= parameter which swap will be used by swsusp? The kernel always uses the first swap device. From kernel/power/Kconfig Note there is currently not a way to specify which device to save the suspended image to. It will simply pick the first available swap device. First swap device, as far as the kernel is concerned, is not the same as first swap device listed in /etc/fstab. That's precisely where pri= makes a difference, and this is precisely what this bug report is about. mkinitrd does NOT use the first swap device, it uses the first entry in /etc/fstab. This is a mass edit of all mkinitrd bugs. Thanks for taking the time to file this bug report (and/or commenting on it). As you may have heard in Fedora 12 mkinitrd has been replaced by dracut. In Fedora 12 the mkinitrd package is still around as some programs depend on certain libraries it provides, but mkinitrd itself is no longer used. In Fedora 13 mkinitrd will be removed completely. This means that all work on initrd has stopped. Rather then keeping mkinitrd bugs open and giving false hope they might get fixed we are mass closing them, so as to clearly communicate that no more work will be done on mkinitrd. We apologize for any inconvenience this may cause. If you are using Fedora 11 and are experiencing a mkinitrd bug you cannot work around, please upgrade to Fedora 12. If you experience problems with the initrd in Fedora 12, please file a bug against dracut. |