LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 01-16-2004, 06:59 AM   #1
demmylls
Member
 
Registered: Aug 2003
Location: AT
Distribution: Fedora Core 3
Posts: 404

Rep: Reputation: 30
All of your loopback devices are in use.


when i compiling kernel 2.6.1 and make bzImage and make modules went fine and no error
but when i wanted to make modules_install the 1st message i got is this and follows with other modules installatin modules name

Mutex destroy failure: Device or resource busy


then i make install i got this error.
its seems like mkinitrd is wrong right?

sh /usr/src/linux-2.6.1/arch/i386/boot/install.sh 2.6.1 arch/i386/boot/bzImage System.map ""
All of your loopback devices are in use.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2

i tried to do this manually

# /sbin/mkinitrd /boot/initrd-2.6.1 2.6.1
All of your loopback devices are in use.

what is all loopback device are in use?
how to fix this?
 
Old 01-16-2004, 04:29 PM   #2
jailbait
LQ Guru
 
Registered: Feb 2003
Location: Virginia, USA
Distribution: Debian 12
Posts: 8,336

Rep: Reputation: 548Reputation: 548Reputation: 548Reputation: 548Reputation: 548Reputation: 548
"what is all loopback device are in use?
how to fix this?"

You can find out how many loopback devices you have with this command:
ls -l /dev/loop*

I have 15 loopback devices on my system and I have never run out. If you need more loopback devices you can create them with the mknod command.

Since you compile your own kernels be sure that loopback device support is enabled in your kernel compile.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites
 
Old 01-16-2004, 05:11 PM   #3
SciYro
Senior Member
 
Registered: Oct 2003
Location: hopefully not here
Distribution: Gentoo
Posts: 2,038

Rep: Reputation: 51
there should be a devices.txt file somewere in the kernel source (i 4get were) it have the all the devices listed along with the numbers that the mknod comand needs, its been a while sence i usd it but it will be something like mknod c * * loop* (you expect me to remember the major and minor numbers for that deice?)
 
Old 01-20-2004, 02:58 PM   #4
fatcat
LQ Newbie
 
Registered: Jan 2004
Posts: 10

Rep: Reputation: 1
Thumbs up

You also need to include loopback support into your kernel. Either as a module or in kernel:
CONFIG_BLK_DEV_LOOP=m

Example:
# sbin/mkinitrd /boot/initrd-2.6.1 2.6.1
WARNING: using /tmp for temporary files
All of your loopback devices are in use.
# /sbin/modprobe loop
# /sbin/mkinitrd /boot/initrd-2.6.1 2.6.1
WARNING: using /tmp for temporary files
# lsmod| grep loop
loop 17256 0
 
Old 04-09-2004, 11:17 PM   #5
debian_dummy
Member
 
Registered: Apr 2004
Distribution: Debian SID and Woody
Posts: 77

Rep: Reputation: 15
I have the same problem. Upgrading 2.4.22 kernel tom2.6 under Fedora core 1.
Everything goes smoothly until "make install" time

Any ideas ?

[root@localhost linux]# make install
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.5/arch/i386/boot/install.sh 2.6.5 arch/i386/boot/bzImage System.map ""
All of your loopback devices are in use.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2
[root@localhost linux]# ls -l /dev/loop*
brw-rw---- 1 root disk 7, 0 Sep 15 2003 /dev/loop0
brw-rw---- 1 root disk 7, 1 Sep 15 2003 /dev/loop1
brw-rw---- 1 root disk 7, 10 Sep 15 2003 /dev/loop10
brw-rw---- 1 root disk 7, 11 Sep 15 2003 /dev/loop11
brw-rw---- 1 root disk 7, 12 Sep 15 2003 /dev/loop12
brw-rw---- 1 root disk 7, 13 Sep 15 2003 /dev/loop13
brw-rw---- 1 root disk 7, 14 Sep 15 2003 /dev/loop14
brw-rw---- 1 root disk 7, 15 Sep 15 2003 /dev/loop15
brw-rw---- 1 root disk 7, 2 Sep 15 2003 /dev/loop2
brw-rw---- 1 root disk 7, 3 Sep 15 2003 /dev/loop3
brw-rw---- 1 root disk 7, 4 Sep 15 2003 /dev/loop4
brw-rw---- 1 root disk 7, 5 Sep 15 2003 /dev/loop5
brw-rw---- 1 root disk 7, 6 Sep 15 2003 /dev/loop6
brw-rw---- 1 root disk 7, 7 Sep 15 2003 /dev/loop7
brw-rw---- 1 root disk 7, 8 Sep 15 2003 /dev/loop8
brw-rw---- 1 root disk 7, 9 Sep 15 2003 /dev/loop9
 
Old 04-09-2004, 11:44 PM   #6
debian_dummy
Member
 
Registered: Apr 2004
Distribution: Debian SID and Woody
Posts: 77

Rep: Reputation: 15
I followed the 2.6 instructions at http://www.linuxquestions.org/questi...threadid=73436

vmlinuz and System.map are created in /boot but there is no initrd-2.6.5.img

I still get the same error using either of the 2 commands below
<<<<<<<<<command 1>>>>>>>>
[root@localhost linux]# /sbin/mkinitrd /boot/initrd-2.6.5.img 2.6.5
All of your loopback devices are in use

<<<<< command 2>>>>>>>>>>>
[root@localhost linux]# make install
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.5/arch/i386/boot/install.sh 2.6.5 arch/i386/boot/bzImage System.map ""
All of your loopback devices are in use.
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2

Last edited by debian_dummy; 04-09-2004 at 11:48 PM.
 
Old 04-21-2004, 11:24 PM   #7
rcgraves
LQ Newbie
 
Registered: Apr 2004
Distribution: RHEL
Posts: 1

Rep: Reputation: 0
Check the permissions and mount options on /tmp. I caused this problem for myself with the following. "nodev" is generally a good idea for security, but it prevents mkinitrd from working.

none /tmp tmpfs nosuid,mode=1777,nodev 0 0
 
Old 07-23-2004, 11:06 AM   #8
ashlock
Member
 
Registered: Jul 2003
Distribution: Fedora Core 2, RH 9
Posts: 33

Rep: Reputation: 15
While all the above suggestions may work in different situations, I found that this problem was fixed for me by simply re-enabling autofs in system-config-services, or with "/sbin/service autofs restart" when compiling kernel 2.6.7

Last edited by ashlock; 07-23-2004 at 11:07 AM.
 
Old 08-02-2004, 12:04 PM   #9
kan4132
LQ Newbie
 
Registered: Jul 2004
Posts: 4

Rep: Reputation: 0
Simply try exiting the kernel you're in and using a different kernel version. I was upgrading my 2.4.22 kernel while using my 2.4.22 kernel and then I rebooted into 2.4.20 kernel and recompiled the kernel and everything worked fine. Hope this works, it's way easier than the other solutions.

PEACE
KAN
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Using loopback interface... ozymandias Linux - Newbie 2 10-28-2005 01:37 PM
all of your loopback devices are in use alaios Linux - General 10 11-14-2004 11:52 PM
Serial loopback max76 Programming 2 10-14-2004 10:24 AM
loopback device praveenv Linux - Newbie 2 08-23-2004 07:27 AM
Loopback won't come up Paul_assheton Linux - Networking 8 05-20-2003 08:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 07:36 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration