From: Andrew Morton <akpm@linux-foundation.org>
To: Andre Noll <maan@systemlinux.org>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
James Bottomley <James.Bottomley@SteelEye.com>,
Jens Axboe <jens.axboe@oracle.com>,
Alasdair G Kergon <agk@redhat.com>, Adrian Bunk <bunk@stusta.de>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: qla2xxx BUG: workqueue leaked lock or atomic
Date: Wed, 7 Mar 2007 11:45:25 -0800 [thread overview]
Message-ID: <20070307114525.08265c33.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070307170955.GA4252@skl-net.de>
On Wed, 7 Mar 2007 18:09:55 +0100 Andre Noll <maan@systemlinux.org> wrote:
> On 20:39, Andrew Morton wrote:
> > On Wed, 28 Feb 2007 16:37:22 +0100 Andre Noll <maan@systemlinux.org> wrote:
> >
> > > On 16:18, Andre Noll wrote:
> > >
> > > > With 2.6.21-rc2 I am unable to reproduce this BUG message. However,
> > > > writing to both raid systems at the same time via lvm still locks up
> > > > the system within minutes.
> > >
> > > Screenshot of the resulting kernel panic:
> > >
> > > http://systemlinux.org/~maan/shots/kernel-panic-21-rc2-huangho2.png
> > >
> >
> > It died in CFQ. Please try a different IO scheduler. Use something
> > like
> >
> > echo deadline > /sys/block/sda/queue/scheduler
> >
> > This could still be the old qla2xxx bug, or it could be a new qla2xxx bug,
> > or it could be a block bug, or it could be an LVM bug.
>
> OK. I'm running with deadline right now. But I guess this kernel
> panic was caused by an LVM bug because lockdep reported problems with
> LVM. Nobody responded to my bug report on the LVM mailing list (see
> http://www.redhat.com/archives/linux-lvm/2007-February/msg00102.html).
>
> Non-working snapshots and no help from the mailing list convinced me
> to ditch the lvm setup [1] in favour of linear software raid. This
> means I can't do lvm-related tests any more.
Sigh.
> BTW: Are ext3 filesystem sizes greater than 8T now officially
> supported?
I think so, but I don't know how much 16TB testing developers and
distros are doing - perhaps the linux-ext4 denizens can tell us?
next parent reply other threads:[~2007-03-07 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070226133153.GC4095@skl-net.de>
[not found] ` <20070226182617.GC9968@andrew-vasquezs-computer.local>
[not found] ` <20070227101100.GA22572@skl-net.de>
[not found] ` <20070227185134.GJ20397@andrew-vasquezs-computer.local>
[not found] ` <20070228151829.GI22572@skl-net.de>
[not found] ` <20070228153722.GJ22572@skl-net.de>
[not found] ` <20070306203952.471218df.akpm@linux-foundation.org>
[not found] ` <20070307170955.GA4252@skl-net.de>
2007-03-07 19:45 ` Andrew Morton [this message]
2007-03-07 20:05 ` qla2xxx BUG: workqueue leaked lock or atomic Mingming Cao
2007-03-09 9:36 ` Andre Noll
2007-03-12 15:22 ` Valerie Clement
2007-03-13 7:01 ` Andreas Dilger
2007-03-13 8:23 ` Valerie Clement
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=20070307114525.08265c33.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@SteelEye.com \
--cc=agk@redhat.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bunk@stusta.de \
--cc=jens.axboe@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=maan@systemlinux.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