From: Mike Panetta <mpanetta@applianceware.com>
To: linux-kernel@vger.kernel.org
Subject: kernel panic when using loop device on kernel 2.4.3
Date: Wed, 18 Apr 2001 14:33:16 -0700 [thread overview]
Message-ID: <20010418143316.A955@tetsuo.applianceware.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
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
--
[-- Attachment #2: ver-linux --]
[-- Type: text/plain, Size: 635 bytes --]
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
next reply other threads:[~2001-04-18 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 21:33 Mike Panetta [this message]
2001-04-18 21:39 ` kernel panic when using loop device on kernel 2.4.3 Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010418143316.A955@tetsuo.applianceware.com \
--to=mpanetta@applianceware.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox