| Summary: | Default 500MB /boot partition is not enough for some use cases | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Banas <mbanas> | |
| Component: | python-blivet | Assignee: | Chris Lumens <clumens> | |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team> | |
| Severity: | unspecified | Docs Contact: | Petr Bokoc <pbokoc> | |
| Priority: | unspecified | |||
| Version: | 7.2 | CC: | agialluc, lmiksik, lsmid, mbanas, pbokoc, riehecky, vpavlin | |
| Target Milestone: | beta | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | python-blivet-0.61.15.43-1 | Doc Type: | Known Issue | |
| Doc Text: |
Insufficient `/boot` partition size may prevent the system from upgrading
The `/boot` partition, which contains installed kernels and initial ram disks, may become full if multiple kernels and additional packages such as _kernel-debug_ are installed. This is caused by the default size of this partition being set to 500 MB during installation, and prevents the system from being upgraded.
As a workaround, use "yum" to remove older kernels if you do not need them.
This known issue only affects installation made with Red Hat Enterprise Linux 7.2 and earlier. In Red Hat Enterprise Linux 7.3, the default size of the `/boot` partition is increased to 1 GB, which avoids this problem in future upgrades.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1370132 (view as bug list) | Environment: | ||
| Last Closed: | 2016-11-03 23:51:26 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: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1186677, 1295926, 1313485, 1366991, 1370132 | |||
|
Description
Martin Banas
2015-10-12 15:14:52 UTC
Expected Result: 1G /boot partition should accomodate 3 kernels without issues. See also: BZ1262098 [1] [1] https://bugzilla.redhat.com/show_bug.cgi?id=1262098 Are there any platform-specific concerns over growing the size of /boot? Will all architectures still be able to see and boot from a filesystem of that size? This requires the following patch be applied to blivet:
diff --git a/blivet/platform.py b/blivet/platform.py
index 8363c0d..df903f5 100644
--- a/blivet/platform.py
+++ b/blivet/platform.py
@@ -165,7 +165,7 @@ class Platform(object):
def set_platform_boot_partition(self):
"""Return the default /boot partition for this platform."""
- return [PartSpec(mountpoint="/boot", size=Size("500MiB"),
+ return [PartSpec(mountpoint="/boot", size=Size("1GiB"),
weight=self.weight(mountpoint="/boot"))]
def set_default_partitioning(self):
@@ -360,7 +360,7 @@ class S390(Platform):
def set_platform_boot_partition(self):
"""Return the default platform-specific partitioning information."""
- return [PartSpec(mountpoint="/boot", size=Size("500MiB"),
+ return [PartSpec(mountpoint="/boot", size=Size("1GiB"),
weight=self.weight(mountpoint="/boot"), lv=False)]
def required_disklabel_type(self, device_type):
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2168.html |