bug in 2.6.22-rc1: loop devices limited to one single device

Hi,

The patch against loop.c is neither a fix, nor does it create
loop devices on demand:

Facts are instead, at least on my machine:

The number of available loop devices is reduced from 8 (conventional
standard of preceding 2.6 kernels) to 1.

The consequence is: If you have to mount more than one single iso-image with
the loop parameter you are receiving the following message during system boot:

"mount: could not find any free loop device"

Regards

Uwe

--
GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Loopback as user
    ... >> I think you have to change the permission on the loop devices, ... I would like do without getting root once. ... they could create a user-writable block dev for ... /etc/fstab), as otherwise a user could mount over /, or mount a volume ...
    (comp.os.linux.misc)
  • Re: mount: could not find any free loop device
    ... > mount: could not find any free loop device ... > they do and if it's them who are using the loop devices. ...
    (Fedora)
  • Re: loop devices removable
    ... modified) pmount to mount them. ... I'm wondering if fuse would be suited better. ...
    (Linux-Kernel)
  • Re: mount: could not find any free loop device
    ... could not find any free loop device ... they do and if it's them who are using the loop devices. ... losetup -d /dev/loop0 ... mount works again. ...
    (Fedora)
  • Re: mount: could not find any free loop device
    ... On 6/27/07, Andras Simon wrote: ... could not find any free loop device ... they do and if it's them who are using the loop devices. ... mount works again. ...
    (Fedora)