DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:date:from:to:cc:subject:message-id:references:mime-version:content-type:content-disposition:in-reply-to:user-agent;
        b=LaSLp46MRLUHqNlMYqr44qCY/FbWHS8U2ymXAGppUSJDOPmH9Pu2/dKfB1i3SkoWI5Gy98ufml6tWfDWlazq5FZqC2wb4DQAtDhODbXFpuB0jsj0mFCrEt0I27pyibSjG9/nYPYyEJexnhdRIcbfRz0AzHHPCGbntGqhluSAjDU=
Date: Thu, 17 May 2007 01:11:46 +0400
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: (1 loop device) Re: [1/3] 2.6.22-rc1: known regressions v2
Message-ID: <20070516211146.GA5660@martell.zuzino.mipt.ru>
References: <464B6A22.905@googlemail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <464B6A22.905@googlemail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1044
Lines: 32

On Wed, May 16, 2007 at 10:31:30PM +0200, Michal Piotrowski wrote:
> Block devices
>
> Subject    : loop devices limited to one single device
> References : http://lkml.org/lkml/2007/5/16/229
> Submitter  : Uwe Bugla <uwe.bugla@gmx.de>
> Status     : Unknown

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

It does. In kernel memory.

>> 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"

I suggest to read mknod(1) manpage.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/