2001-04-18 21:34:07

by Mike Panetta

[permalink] [raw]
Subject: kernel panic when using loop device on kernel 2.4.3

I have been getting kernel panics on kernel 2.4.3
when using the loop device on a rather regular basis.
I get a kernel panic but no oops message. The kernel
panic message says Kernel panic: invalid blocksize passed
to set_blocksize. I saw that someone else on the list
has had these problems as well but I have seen no response.
Has a fix for this bug been posted that I have not seen?
Is the fix in any current stable or AC kernel? As far as
I know I am not using any strange options. The only thing
I can think of would be that multiple people are using the
loopback device at the same time. This is because the box
that is having the problems is a build server for a custom
software distro. We use the loopback filesystem to create
the boot image. The box is a 4way xeon with 1GB of ram.
Are there any known issues with loopback and SMP? Or even
loopback and multiple mounts/usage?

ver_linux output attached.

Thanks,
Mike
--


Attachments:
(No filename) (939.00 B)
ver-linux (635.00 B)
Download all attachments

2001-04-18 21:40:07

by Jens Axboe

[permalink] [raw]
Subject: Re: kernel panic when using loop device on kernel 2.4.3

On Wed, Apr 18 2001, Mike Panetta wrote:
> I have been getting kernel panics on kernel 2.4.3
> when using the loop device on a rather regular basis.
> I get a kernel panic but no oops message. The kernel
> panic message says Kernel panic: invalid blocksize passed
> to set_blocksize. I saw that someone else on the list
> has had these problems as well but I have seen no response.

There was a response, I just didn't have time to look at the problem
just yet.

> Has a fix for this bug been posted that I have not seen?
> Is the fix in any current stable or AC kernel? As far as
> I know I am not using any strange options. The only thing
> I can think of would be that multiple people are using the
> loopback device at the same time. This is because the box
> that is having the problems is a build server for a custom
> software distro. We use the loopback filesystem to create
> the boot image. The box is a 4way xeon with 1GB of ram.

For now, just losetup and don't mount directly -- the previous report
had something to do with that, so I'm assuming that's part of the reason
at least.

> Are there any known issues with loopback and SMP? Or even
> loopback and multiple mounts/usage?

No

--
Jens Axboe