Bug 502181 - insmod: error inserting "/lib/ext4.ko": -1 File exists
Summary: insmod: error inserting "/lib/ext4.ko": -1 File exists
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mkinitrd
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Hans de Goede
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-22 11:42 UTC by Michal Babej
Modified: 2013-07-31 23:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-29 11:38:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of boot (19.00 KB, image/png)
2009-05-22 11:47 UTC, Michal Babej
no flags Details
mkinitrd log (103.60 KB, text/plain)
2009-06-29 11:03 UTC, Michal Babej
no flags Details

Description Michal Babej 2009-05-22 11:42:21 UTC
Description of problem:
'insmod: error inserting "/lib/ext4.ko": -1 File exists' message is displayed on boot, and the boot is very slow. /etc/fstab content:

LABEL=/                 /                       ext4dev defaults        1 1
LABEL=/boot             /boot                   ext2    defaults        1 2
tmpfs                   /dev/shm                tmpfs   defaults        0 0
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
sysfs                   /sys                    sysfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
LABEL=SWAP-vda1         swap                    swap    defaults        0 0



Version-Release number of selected component (if applicable):
kernel -148 and -149; does not appear on -141

How reproducible:
always

Comment 1 Michal Babej 2009-05-22 11:47:18 UTC
Created attachment 345084 [details]
screenshot of boot

Comment 3 Hans de Goede 2009-06-29 09:44:18 UTC
Hi,

Can you please run:
bash -x /sbin/mkinitrd -f test.img $(uname -r) &> log

On an affected system and attach the resulting log file here?

Thank you!

Comment 4 Michal Babej 2009-06-29 11:03:25 UTC
Created attachment 349769 [details]
mkinitrd log

Actually, IIRC this has been solved in the next kernel update (150.el5; at the same time mkinitrd was updated to -53 from -51); still, here's the log from that command.

Comment 5 Hans de Goede 2009-06-29 11:38:34 UTC
Judging from the log file, this indeed is no longer happening, closing.


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