On Fri, 15 Jun 2007 12:19:35 +0100
"Simon Arlott" <[EMAIL PROTECTED]> wrote:
> > It *is* a good idea. MD works that way too.
>
> There's a patch around somewhere to create at least 8 devices, I don't know
> why it's not in Linus' tree yet...
It is! It's just that it was applied after -rc4...
On Fri, June 15, 2007 10:01, Jan Engelhardt wrote:
>
> On Jun 14 2007 14:52, markus reichelt wrote:
>>* Matthew <[EMAIL PROTECTED]> wrote:
>>
>>> I read that now loop devices are being created on demand, which
>>> obviously (still) not works
>>
>>yes, someone thought this was a good idea :(
>
> It
On Jun 14 2007 18:32, Matthias Schniedermeyer wrote:
> markus reichelt wrote:
>
>> PS: Just wondering: Who came up with this "on-demand" hype?
>
> I don't remember the names, but i remember the root causes. Here we go:
http://lkml.org/lkml/2007/3/22/86
Jan
--
-
To unsubscribe from thi
On Jun 14 2007 14:52, markus reichelt wrote:
>* Matthew <[EMAIL PROTECTED]> wrote:
>
>> I read that now loop devices are being created on demand, which
>> obviously (still) not works
>
>yes, someone thought this was a good idea :(
It *is* a good idea. MD works that way too.
Jan
--
-
To
markus reichelt wrote:
PS: Just wondering: Who came up with this "on-demand" hype?
I don't remember the names, but i remember the root causes. Here we go:
The discussion started when someone with a CD-Server ran out of loops as 256 was the
"fixed" maximum.
The other "root"-cause was that th
* Paolo Ornati <[EMAIL PROTECTED]> wrote:
> So with this patch "max_loop=32" will create 32 loop devices... but
> then it doesn't allow more of them.
Well, that's what a max_ parameter implies ;p
A manually set limit of loop devices is ok with me. (32 was just an
example -- After all, I could ha
On Thu, 14 Jun 2007 16:10:44 +0200
Matthew <[EMAIL PROTECTED]> wrote:
> I just tried out
>
> modprobe loop max_loop=32
>
> output of dmesg is:
>
> [ 457.607575] loop: the max_loop option is obsolete and will be
> removed in March 2008
> [ 457.607578] loop: module loaded
>
> but there are NO
Thanks, Paolo, Markus,
I just tried out
modprobe loop max_loop=32
output of dmesg is:
[ 457.607575] loop: the max_loop option is obsolete and will be
removed in March 2008
[ 457.607578] loop: module loaded
but there are NO loop devices in /dev:
ls -l /dev/ | grep loop
still shows nothing,
On Thu, 14 Jun 2007 13:37:32 +0200
Matthew <[EMAIL PROTECTED]> wrote:
> now back to topic:
>
> /dev/loop* seems to be broken since (at least) 2.6.22-rc3, since that
> was the first kernel I tried of the 2.6.22-rc* series
>
> ls -l /dev/ | grep loop
>
> shows no output
Yes, now the "loop" devic
* Matthew <[EMAIL PROTECTED]> wrote:
> I read that now loop devices are being created on demand, which
> obviously (still) not works
yes, someone thought this was a good idea :(
> Is there a way to trigger such creation?
does modprobe loop max_loop=32 work?
--
left blank, right bald
pgp1Dm
Hi everybody,
this is my first post on this list & I hope I'm doing everything right
first off all: many thanks to everyone who makes GNU/Linux such a
great system :)
now back to topic:
/dev/loop* seems to be broken since (at least) 2.6.22-rc3, since that
was the first kernel I tried of the 2.
11 matches
Mail list logo
