Bug 1346231
Summary: | unbootable after removing swap partition | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Steigerwald <martin.steigerwald> | ||||||
Component: | dracut | Assignee: | Lukáš Nykrýn <lnykryn> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 7.2 | CC: | dracut-maint-list | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2020-12-15 07:42:10 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Martin Steigerwald
2016-06-14 10:28:08 UTC
Created attachment 1167831 [details]
rdsosreport for booting without swap
One additional note:
To have the system booting again I just recreated the swap volume and did a swap on it, and correctly the booted system did not have swap mounted, cause I removed it from /etc/fstab already.
So it could not be used for hibernation anyway anymore.
But yet, for the hibernation case:
I think a system may *never* *ever* boot an outdated hibernation image, as it can create severe data loss (been there, recovered from it via xfs_repair years ago). It may be a challenge to make sure of that, but I think storing a hibernation id both in the hibernation image and in /boot/something would enable to initrd to check whether the hibernation image is still valid. On any boot, be it a boot with resuming or a successful resume remove hibernation id from /boot/something again. And if the hibernation id in /boot/something is not there or does not match the hibernation id in the image, then do *not* resume.
So in case of a accidentally non working swap, it may not resume, but the that is not more severe than a sudden power loss.
"a boot without resuming or a successful resume" of course After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |