Bug 438743 - mkinitrd creates initrd.img/init script with ~6000 insmod lines for lock_nolock.ko, and gfs2.ko
mkinitrd creates initrd.img/init script with ~6000 insmod lines for lock_nolo...
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Peter Jones
Depends On:
  Show dependency treegraph
Reported: 2008-03-24 16:10 EDT by James Laska
Modified: 2013-09-02 02:24 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2008-0437
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-21 11:26:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
/var/log/messages (23.60 KB, text/plain)
2008-03-24 16:10 EDT, James Laska
no flags Details
/init (from /boot/initrd-2.6.18-86.el5.img) (169.64 KB, text/plain)
2008-03-24 16:11 EDT, James Laska
no flags Details

  None (edit)
Description James Laska 2008-03-24 16:10:25 EDT
Description of problem:

Perform a kickstart install with the root partition being a logical volume of

On boot up ... observe the following message on console:

124:Mar 24 12:59:57 ibm-505-lp1 kernel: lock_nolock: Unknown symbol
125:Mar 24 12:59:58 ibm-505-lp1 kernel: lock_nolock: Unknown symbol
126:Mar 24 12:59:58 ibm-505-lp1 kernel: GFS2 (built Mar 18 2008 18:27:16) installed
184:Mar 24 12:59:58 ibm-505-lp1 kernel: GFS2: fsid=: Trying to join cluster
"lock_nolock", "dm-0"
185:Mar 24 12:59:58 ibm-505-lp1 kernel: GFS2: fsid=dm-0.0: Joined cluster. Now
mounting FS...
186:Mar 24 12:59:58 ibm-505-lp1 kernel: GFS2: fsid=dm-0.0: jid=0, already locked
for use
187:Mar 24 12:59:59 ibm-505-lp1 kernel: GFS2: fsid=dm-0.0: jid=0: Looking at
188:Mar 24 12:59:59 ibm-505-lp1 kernel: GFS2: fsid=dm-0.0: jid=0: Done

In discussion with Chris Feist, the lock_nolock.ko module should not be loaded
before gfs2.ko.  Investigating the module load order as defined by the mkinitrd
'init' script ...

Additionally, during install the following error message appears during %post on
the kernel scriptlet:

Installing kernel - 2.6.18-86.el5.ppc64
cpio: ./sbin: Invalid argument
cpio: ./dev/ram: Invalid argument
cpio: ./bin/modprobe: Invalid argument

(full install.log available at

Version-Release number of selected component (if applicable):

 - anaconda-
 - kernel-2.6.18-86.el5
 - mkinitrd-

How reproducible:
100% so far 

Steps to Reproduce:
1. perform kickstart install with root as a logical volume formatted as gfs2
Actual results:
Error messages observed during bootup, and in install.log 

Expected results:
No error messages during bootup and correct module load order defined in the

Additional info:
Comment 1 James Laska 2008-03-24 16:10:25 EDT
Created attachment 298938 [details]
Comment 2 James Laska 2008-03-24 16:11:10 EDT
Created attachment 298939 [details]
/init (from /boot/initrd-2.6.18-86.el5.img)
Comment 3 James Laska 2008-03-24 16:12:24 EDT
Catching this during install shows that the %post is taking a *long* time and
chewing up a lot of cpu in generating all those 6000 module entries :)

  678 0        S       147M   487  0.0  3.7 anaconda
 1440 0        R      62464  1431 99.7  1.5 mkinitrd
Comment 4 James Laska 2008-03-24 16:14:14 EDT
Doing the same test on x86_64 ends differently ... I see the following on the

 /sbin/new-kernel-pkg: line 242: 12326 Segmentation fault      /sbin/mkinitrd
--allow-missing -f $initrdfile $version
mkinitrd failed
sending termination signals...done
sending kill signals...done
disabling swap...
unmounting filesystems...
Comment 6 James Laska 2008-03-28 08:05:48 EDT
Looks like a similar problem surfacing in bug#439371
Comment 9 James Laska 2008-03-28 13:02:03 EDT
tburke: Customer will see this issue as follows:

* Kernel panic on post-install bootup on i386, ia64, x86_64
* Delayed install on ppc
Comment 12 Peter Jones 2008-03-28 17:37:09 EDT
Fixed in mkinitrd- .
Comment 14 James Laska 2008-03-31 09:36:17 EDT
VERIFIED in RHEL5.2-Server-20080331.nightly (mkinitrd-

# grep -n "\(gfs2\|lock\)" ./init 
41:echo Creating block device nodes.
50:echo "Loading gfs2.ko module"
51:insmod /lib/gfs2.ko 
52:echo "Loading lock_nolock.ko module"
53:insmod /lib/lock_nolock.ko 
73:lvm vgscan --ignorelockingfailure
75:lvm vgchange -ay --ignorelockingfailure  vg01
78:mkrootdev -t gfs2 -o defaults,ro /dev/vg01/lv_root
Comment 16 errata-xmlrpc 2008-05-21 11:26:43 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.