Bug 122325
| Summary: | mkinitrd default initrd size too small for 2.6.5 kernel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Howard Wilkinson <howard> | ||||
| Component: | mkinitrd | Assignee: | Jeremy Katz <katzj> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | barryn, benhsu | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 3.5.22-1 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-08-02 21:58:33 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: | |||||||
| Attachments: |
|
||||||
Created attachment 99898 [details]
Patch to imagesize for mkinitrd and new-kernel-pkg
Add a option to mkinitrd for the imagesize and use this from new-kernel-pkg to
set the size to 12000
This route isn't as good as the ramdisk size in the kernel is only set ot 8 megs. So I bumped to 8 megs across the board in mkinitrd. This route isn't as good as the ramdisk size in the kernel is only set ot 8 megs. So I bumped to 8 megs across the board in mkinitrd. Increasing the kerneal RAM disk is not going to fix this problem. The images run out of space at 8 megs when being built. I am having to run the kernel we boot with 32 Meg RAMDISKS. (16 Meg was failing and I only tried a power of 2). You need this fix to build the anaconda images for the pxeboot with aic7xxx, LVM and RAID drivers plus e100 or e1000 drivers in my case (which also needs mii). Another fix is needed if you embed these drivers in the kernel as new-kernel-img fails to account for mkinitrd reporting it cannot find a module (already built in) and of course does not provide any interface to tell mkinitrd that this is so. I believe I am hitting this bug. The initrd generated is only ~100K compared to ~200K for the initrd shipped. This happens even when I compile the kernel shipped with FC2. Does this sound like this bug or should I open a new bug? FC2 I appear to ge hitting this as well, was wondering why the files were so much smaller. I also noticed that I would get random sizes for my initrd when trying to create one manually. 276009 initrd-2.4.20-20.9.img 191404 initrd-2.6.5-1.358smp.img Tried mkinitrd-3.5.23-1 as well, no joy. Regards, Ted With mkinitrd-4.x, we're moving to the creation of an initramfs instead of an initrd and thus shouldn't hit this anymore |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) Description of problem: Mkinitrd runs out of space when creating a 2.6.5 initrd for i686 platform. The size in the code is 4000 for an i386 box and 8000 for an i686 box. The machines being used require aic7xxx, dm-mod, raid0, scsi_mod, sd_mod, jbd and ext3 to be preloaded to operate. I have a patch that allows the size to be specified to mkinitrd on the command line and a patch to new-kernel-pkg to increase the size to 12000 by default. Version-Release number of selected component (if applicable): mkinitrd-3.5.21-1 How reproducible: Always Steps to Reproduce: 1.Try to install a kernel on a machine with modules requirements as above 2.Fails 3. Actual Results: Kernel would not boot properly as the modules did not exist. Expected Results: Kernel boots when fixed. Additional info: