[EMAIL PROTECTED] said:
> Well, I wrote the script. It has been running for 10 minutes now
> mounting and unmounting an iso image. Nothing happens. I guess I
> should be happy. Still don't undertand where the original Oops came
> from
It's a great shame that your distribution vendor shipped k
On Mon, Apr 16 2001, Ian Eure wrote:
> Jens Axboe writes:
> > On Wed, Apr 11 2001, Ian Eure wrote:
> > > i get this message when it panics:
> > >
> > > -- snip --
> > > loop: setting 534781920 bs for 07:86
> > > Kernel panic: Invalid blocksize passed to set_blocksize
> > > -- snip --
> >
On Mon, Apr 16 2001, Alexander Viro wrote:
>
>
> On Mon, 16 Apr 2001, Jens Axboe wrote:
>
> > > I can mount the same file on the same mountpoint more than once. If I
> > > mount a file twice (same file on the same mount point)
> >
> > This is a 2.4 feature
>
> Ability to losetup different loo
On Mon, Apr 16 2001, Mircea Damian wrote:
> But the guy said:
> "
> > disappers from cat /proc/mounts output, but the module 'loop' shows as
> > busy and cannot be removed even though there are no more loop mounts.
> "
>
> So he has no loop mounts and he can not remove the module. This is a bug!
Jens Axboe writes:
> On Wed, Apr 11 2001, Ian Eure wrote:
> > i get this message when it panics:
> >
> > -- snip --
> > loop: setting 534781920 bs for 07:86
> > Kernel panic: Invalid blocksize passed to set_blocksize
> > -- snip --
>
> Ahm, how are you setting your loop device up? The a
On Mon, Apr 16, 2001 at 05:30:45AM -0400, Alexander Viro wrote:
>
>
> On Mon, 16 Apr 2001, Jens Axboe wrote:
>
> > > I can mount the same file on the same mountpoint more than once. If I
> > > mount a file twice (same file on the same mount point)
> >
> > This is a 2.4 feature
>
> Ability to
On Mon, 16 Apr 2001, Jens Axboe wrote:
> > I can mount the same file on the same mountpoint more than once. If I
> > mount a file twice (same file on the same mount point)
>
> This is a 2.4 feature
Ability to losetup different loop devices to the same underlying
file is a bug, though. Not tha
On Sun, Apr 15 2001, Arthur Pedyczak wrote:
> On Sat, 14 Apr 2001, Jeff Garzik wrote:
>
> > Can you try 2.4.4-pre3?
> > ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
> >
> I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something
> disturbing:
>
> I can mount the same file o
On Sun, 15 Apr 2001, Arthur Pedyczak wrote:
> On Sat, 14 Apr 2001, Jeff Garzik wrote:
>
> > Can you try 2.4.4-pre3?
> > ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
> >
...the same thing happens in 2.4.3...
> I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something
> d
On Sat, 14 Apr 2001, Jeff Garzik wrote:
> Can you try 2.4.4-pre3?
> ftp://ftp.us.kernel.org/pub/linux/kernel/testing/
>
I am testing loop behaviour in 2.4.3 and 3.4.4p3. I have noticed something
disturbing:
I can mount the same file on the same mountpoint more than once. If I
mount a file twice
gt; CC: Linux kernel list <[EMAIL PROTECTED]>; Jeff Garzik
> <[EMAIL PROTECTED]>
> Sent: Sat Apr 14 08:46:49 2001
> Subject: Re: loop problems continue in 2.4.3
>
> On Sat, 14 Apr 2001, Jens Axboe wrote:
>
> [ SNIP..]
> > > =
MAIL PROTECTED]>
Sent: Sat Apr 14 08:46:49 2001
Subject: Re: loop problems continue in 2.4.3
On Sat, 14 Apr 2001, Jens Axboe wrote:
[ SNIP..]
> > =
> > Apr 13 20:50:03 cs865114-a kernel: Unable to handle kernel paging
request at virtual address 7e
To: "Jens Axboe" <[EMAIL PROTECTED]>
Cc: "Linux kernel list" <[EMAIL PROTECTED]>; "Jeff Garzik"
<[EMAIL PROTECTED]>
Sent: Saturday, April 14, 2001 2:46 PM
Subject: Re: loop problems continue in 2.4.3
> On Sat, 14 Apr 2001, Jens Axboe wrote:
>
>
On Sat, 14 Apr 2001, Jens Axboe wrote:
[ SNIP..]
> > =
> > Apr 13 20:50:03 cs865114-a kernel: Unable to handle kernel paging request at
>virtual address 7e92bfd7
>
> Please disable syslog decoding (it sucks) and feed it through ksymoops
> instead.
>
> In other
On Fri, Apr 13 2001, Arthur Pedyczak wrote:
> Hi all,
> here are my $0.02 regarding loop in 2.4.3.
>
> 1. mounted file
> mount -t iso9660 -o loop file.img /mnt/cdrom
> worked o.k.
> 2. unmounted
> umount /mnt/cdrom
> worked o.k.
> 3. mounted file
> mount -t iso9660 -o loop file.img /mnt/c
Hi all,
here are my $0.02 regarding loop in 2.4.3.
1. mounted file
mount -t iso9660 -o loop file.img /mnt/cdrom
worked o.k.
2. unmounted
umount /mnt/cdrom
worked o.k.
3. mounted file
mount -t iso9660 -o loop file.img /mnt/cdrom
worked o.k.
4. tried to unmount
umount /mnt/cdrom
got
On Wed, Apr 11 2001, Ian Eure wrote:
> i get this message when it panics:
>
> -- snip --
> loop: setting 534781920 bs for 07:86
> Kernel panic: Invalid blocksize passed to set_blocksize
> -- snip --
Ahm, how are you setting your loop device up? The above is completely
bogus.
--
Jens Axboe
-
T
i get this message when it panics:
-- snip --
loop: setting 534781920 bs for 07:86
Kernel panic: Invalid blocksize passed to set_blocksize
-- snip --
Jens Axboe writes:
> On Sat, Apr 07 2001, Ian Eure wrote:
> > i'm still having loopback problems with linux 2.4.3, even though they
> > were su
On Sat, Apr 07 2001, Ian Eure wrote:
> i'm still having loopback problems with linux 2.4.3, even though they
> were supposed to be fixed. it doesn't deadlock my maching right away
> anymore, but instead causes a kernel panic after 4-6 uses of the loop
> device.
>
> the message i get is: "Kernel p
i'm still having loopback problems with linux 2.4.3, even though they
were supposed to be fixed. it doesn't deadlock my maching right away
anymore, but instead causes a kernel panic after 4-6 uses of the loop
device.
the message i get is: "Kernel panic: Invalid blocksize passed to
set_blocksize"
20 matches
Mail list logo
