Bug 1844423
Summary: | /boot size 200Mib is not enough | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | fujiwara <tfujiwar> |
Component: | anaconda | Assignee: | Vendula Poncova <vponcova> |
Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | --- | CC: | bootloader-eng-team, fmartine, jikortus, jkonecny, jstodola, rharwood, vslavik |
Target Milestone: | rc | Keywords: | Reopened, Triaged |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | anaconda-33.16.7.9-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-08 09:17: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: |
Description
fujiwara
2020-06-05 11:35:52 UTC
Just some data from a freshly installed RHEL-8.2 x86_64 system and after installing kernel updates: The content of /boot after installation of the default package set: [root@localhost ~]# df -h /boot/ Filesystem Size Used Avail Use% Mounted on /dev/vda1 1014M 229M 786M 23% /boot [root@localhost ~]# ls -l /boot/ total 188216 -rw-------. 1 root root 3909996 Mar 27 15:47 System.map-4.18.0-193.el8.x86_64 -rw-r--r--. 1 root root 187648 Mar 27 15:47 config-4.18.0-193.el8.x86_64 drwxr-xr-x. 3 root root 17 Jun 5 14:36 efi drwx------. 4 root root 83 Jun 5 14:52 grub2 -rw-------. 1 root root 98311174 Jun 5 14:41 initramfs-0-rescue-bea028befae442a48899ed35436b5a02.img -rw-------. 1 root root 52726476 Jun 5 14:43 initramfs-4.18.0-193.el8.x86_64.img -rw-------. 1 root root 19756532 Jun 5 14:49 initramfs-4.18.0-193.el8.x86_64kdump.img drwxr-xr-x. 3 root root 21 Jun 5 14:39 loader -rwxr-xr-x. 1 root root 8913760 Jun 5 14:40 vmlinuz-0-rescue-bea028befae442a48899ed35436b5a02 -rwxr-xr-x. 1 root root 8913760 Mar 27 15:48 vmlinuz-4.18.0-193.el8.x86_64 [root@localhost ~]# After installing 3 kernel updates (3 kernels are kept on the system by default, older kernel versions are removed when installing another kernel update): [root@localhost ~]# df -h /boot/ Filesystem Size Used Avail Use% Mounted on /dev/vda1 1014M 406M 609M 40% /boot [root@localhost ~]# ls -l /boot/ total 368900 -rw-------. 1 root root 3963107 May 28 16:29 System.map-4.18.0-208.el8.x86_64 -rw-------. 1 root root 3963107 Jun 2 09:16 System.map-4.18.0-209.el8.x86_64 -rw-------. 1 root root 3965684 Jun 3 14:13 System.map-4.18.0-210.el8.x86_64 -rw-r--r--. 1 root root 188331 May 28 16:29 config-4.18.0-208.el8.x86_64 -rw-r--r--. 1 root root 188402 Jun 2 09:16 config-4.18.0-209.el8.x86_64 -rw-r--r--. 1 root root 188778 Jun 3 14:13 config-4.18.0-210.el8.x86_64 drwxr-xr-x. 3 root root 17 Jun 5 14:36 efi drwx------. 4 root root 83 Jun 5 14:52 grub2 -rw-------. 1 root root 98311174 Jun 5 14:41 initramfs-0-rescue-bea028befae442a48899ed35436b5a02.img -rw-------. 1 root root 19756532 Jun 5 14:49 initramfs-4.18.0-193.el8.x86_64kdump.img -rw-------. 1 root root 50605799 Jun 5 15:29 initramfs-4.18.0-208.el8.x86_64.img -rw-------. 1 root root 19765921 Jun 5 15:30 initramfs-4.18.0-208.el8.x86_64kdump.img -rw-------. 1 root root 50604371 Jun 5 15:32 initramfs-4.18.0-209.el8.x86_64.img -rw-------. 1 root root 19764550 Jun 5 15:32 initramfs-4.18.0-209.el8.x86_64kdump.img -rw-------. 1 root root 50605813 Jun 5 15:35 initramfs-4.18.0-210.el8.x86_64.img -rw-------. 1 root root 19765391 Jun 5 15:35 initramfs-4.18.0-210.el8.x86_64kdump.img drwxr-xr-x. 3 root root 21 Jun 5 14:39 loader -rwxr-xr-x. 1 root root 8913760 Jun 5 14:40 vmlinuz-0-rescue-bea028befae442a48899ed35436b5a02 -rwxr-xr-x. 1 root root 9052816 May 28 16:29 vmlinuz-4.18.0-208.el8.x86_64 -rwxr-xr-x. 1 root root 9052816 Jun 2 09:17 vmlinuz-4.18.0-209.el8.x86_64 -rwxr-xr-x. 1 root root 9061008 Jun 3 14:14 vmlinuz-4.18.0-210.el8.x86_64 [root@localhost ~]# Javier could you please bring some insights here for why we have 200MB recommendation now and how we should proceed? I'm confused since I see in the Anaconda source code that 200 MiB is for /boot/efi and for /boot is 1GiB. So not sure from where the 200 MiB for /boot is coming from. Here is the recommended minimal size defined: https://github.com/rhinstaller/anaconda/blob/rhel-8/data/anaconda.conf#L201 And it's probably from times when 200 MiB was enough... So it should be enough to just adjust the minimal value to avoid having the 200MB size of /boot? If yes, should we use 1G as minimal? Could you please confirm the above? From my user perspective, I guess /boot 1GiB is too much for virtual hosts? I assign 30GB to a virtual host size and two kernels are enough for me in every update. The default size of the partition is 1 GiB. The 200 MiB value is for warning the user in GUI. The warning can be dismissed, so the reason why it matters is that people read it and think it's correct. So bumping it to some reasonable value is probably ok. What would the value be? In the upstream bug, the size is calculated to be a bit more than 300 MiB, so I suggested 512... https://bugzilla.redhat.com/show_bug.cgi?id=1907245 https://github.com/rhinstaller/anaconda/pull/3302 Upstream change merged. Let's give it a week and see if anything breaks, backporting this should be 5 minutes, just like upstream. 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. Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/4095 Checked that anaconda-33.16.7.9-1.el8 is in nightly compose RHEL-8.7.0-20220809.0 Moving to VERIFIED 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 (anaconda bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:7462 |