mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Uwe Bugla" <uwe.bugla@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
	viro@zeniv.linux.org.uk, kenchen@google.com
Subject: bug in 2.6.22-rc1: loop devices limited to one single device
Date: Wed, 16 May 2007 17:08:31 +0200	[thread overview]
Message-ID: <20070516150831.292350@gmx.net> (raw)

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

                 reply	other threads:[~2007-05-16 15:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070516150831.292350@gmx.net \
    --to=uwe.bugla@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome