Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Since the replacement of mkinitrd with dracut in 6.2, initramfs files created automatically seem to have tripled in size for the same hardware. In RHEL5 and previous releases, mkinitrd built an initrd that was customised for this particular machine. In 6.x it seems the opposite approach has been taken and the initramfs that is built contains modules for hardware that is not present.
Version-Release number of selected component (if applicable):
dracut-004-256.el6.noarch
How reproducible:
Always
Steps to Reproduce:
1. Install a new kernel, examine the initramfs created
2. Change /etc/dracut.conf to hostonly="yes"
3. Reinstall same kernel
4. See newly created initramfs is now approximately 1/3rd the size it was before but still functions perfectly for this hardware
Actual results:
On a Dell m610 blade, the initramfs created by default install is 23MB. With hostonly="yes" this drops to 5.5MB.
Expected results:
Smaller files, faster kernel install times, faster boot times.
Additional info:
This not only uses extra disk space in /boot - so 23MB + 4MB for the kernel and 2MB for the System map is close to 30MB per kernel and with a default installonly limit of 5 that takes us to 150MB used. It also means that a kernel install takes much longer than it ought because this huge file has to be created, written and compressed and also the inverse, during boot it has to be read, uncompressed and written out thus extending boot times unnecessarily.
Suggestion: hostonly="yes" should be made default to better emulate RHEL5 and previous releases. Those sysadmins that require to generate a multi-machine initramfs are better qualified to change the default from hostonly="yes" to no than the majority of users. In addition... why is it /etc/dracut.conf and not /etc/sysconfig/dracut to fit in with existing standard file locations?
Suggestion rejected for RHEL-6. It should be the way it is now.
If you set hostonly="yes", you opt out of hardware compatibility and it is your own risk, if you change devices, which need other drivers for the boot process.