From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: Nathan Scott <nathans@sgi.com>
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>,
tes@sgi.com, xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4
Date: Fri, 30 Jun 2006 09:48:05 +0200 [thread overview]
Message-ID: <20060630074805.GE6003@charite.de> (raw)
In-Reply-To: <20060630081420.A1371683@wobbly.melbourne.sgi.com>
* Nathan Scott <nathans@sgi.com>:
> On Thu, Jun 29, 2006 at 10:38:09PM +0200, Ralf Hildebrandt wrote:
> > 2.6.17-mm3 and mm4 both report a "BUG: held lock freed!" while booting
> > up. Find the two dmesg outputs attached.
>
> Thanks Ralf,
>
> From the traces, looks like it happens during the unlinked inode list
> processing, just after log recovery (I assume you crashed / rebooted
> without unmounting before this boot?).
Absolutely. The root-fs could not be umounted correctly, since the -mm3 and
-mm4 Kernels sometime produce unkillable processes. One of these
processes had files open on /, thus the reboot left me with an unclean
XFS fs!
--
_________________________________________________
Charité - Universitätsmedizin Berlin
_________________________________________________
Ralf Hildebrandt
i.A. Geschäftsbereich Informationsmanagement
Campus Benjamin Franklin
Hindenburgdamm 30 | Berlin
Tel. +49 30 450 570155 | Fax +49 30 450 570962
Ralf.Hildebrandt@charite.de
http://www.charite.de
prev parent reply other threads:[~2006-06-30 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 20:38 BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4 Ralf Hildebrandt
2006-06-29 22:14 ` Nathan Scott
2006-06-30 5:35 ` Timothy Shimmin
2006-06-30 7:48 ` Ralf Hildebrandt [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=20060630074805.GE6003@charite.de \
--to=ralf.hildebrandt@charite.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=tes@sgi.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.