From: Jens Axboe <axboe@suse.de>
To: Mike Panetta <mpanetta@applianceware.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel panic when using loop device on kernel 2.4.3
Date: Wed, 18 Apr 2001 23:39:28 +0200 [thread overview]
Message-ID: <20010418233928.K501@suse.de> (raw)
In-Reply-To: <20010418143316.A955@tetsuo.applianceware.com>
In-Reply-To: <20010418143316.A955@tetsuo.applianceware.com>; from mpanetta@applianceware.com on Wed, Apr 18, 2001 at 02:33:16PM -0700
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
prev parent reply other threads:[~2001-04-18 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-18 21:33 kernel panic when using loop device on kernel 2.4.3 Mike Panetta
2001-04-18 21:39 ` Jens Axboe [this message]
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=20010418233928.K501@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpanetta@applianceware.com \
/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