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
If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes.
Linux optimus.applianceware.com 2.4.3 #2 SMP Wed Apr 18 06:00:29 PDT 2001 i686 unknown
Gnu C 2.96 Gnu make 3.79.1 binutils 2.10.91.0.2 util-linux 2.10r modutils 2.4.2 e2fsprogs 1.19 reiserfsprogs 3.x.0b Linux C Library 2.2.2 Dynamic linker (ldd) 2.2.2 Procps 2.0.7 Net-tools 1.57 Console-tools 0.3.3 Sh-utils 2.0
Modules Loaded
Quoted 6 lines · Mike Panetta
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.
Quoted 8 lines
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.
Quoted 2 lines
Are there any known issues with loopback and SMP? Or even loopback and multiple mounts/usage?
No
Signature · 1 line
Jens Axboe