LinuxQuestions.org - "All of your loopback devices are in use." "could not fork"

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - "All of your loopback devices are in use." "could not fork" (https://www.linuxquestions.org/questions/linux-software-2/all-of-your-loopback-devices-are-in-use-could-not-fork-448103/)

"All of your loopback devices are in use." "could not fork"

When trying to use mkinitrd, with a 2.4.32 kernel using devfs, i get:

Code:

All of your loopback devices are in use.

Code:

[root@emu-5 linux]# ls /dev

cdroms  cua    floppy  i2c      initrd  log    loop1  loop4  loop7  md    null  pts    rd        scsi  tts  tty1  tty4  tty7  urandom  vcc

console  discs  full    ide      input  loop  loop2  loop5  loop8  mem  port  pty    root      shm    tty  tty2  tty5  tty8  usb      VolGroup00

cpu      fb    gpmctl  initctl  kmem    loop0  loop3  loop6  mapper  misc  ptmx  random  root.old  sound  tty0  tty3  tty6  tty9  vc      zero

[root@emu-5 linux]# ls /dev/loop

0  1  2  3  4  5  6  7

Any ideas here?

I also have another problem, on another computer running a 2.4.32 kernel, when i try to use a qdisc with tc, in my dmesg i see:

Code:

[root@emu-5 linux]# dmesg

request_module[custom_module]: fork failed, errno 1

This module works perfectly on the other computer, i'm guessing this is another environment problem. What could cause a fork to fail?

Thanks!
George

by the way, the loopback error comes from this in mkinitrd:

Code:

LODEV=$(echo findlodev $modName.o | /sbin/nash --quiet)



if [ -z "$LODEV" ]; then

    rm -rf $MNTPOINT $IMAGE

    echo "All of your loopback devices are in use." >&2

    exit 1

fi

solved

i dual boot, and it was using modprobe/insmod/rmmod from 2.6 module-utils instead of 2.4 modutils