[Top] [All Lists]

Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4
From: Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx>
Date: Fri, 30 Jun 2006 09:48:05 +0200
Cc: Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx>, tes@xxxxxxx, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20060630081420.A1371683@xxxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Nathan Scott <nathans@xxxxxxx>, tes@xxxxxxx, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
References: <20060629203809.GD20456@xxxxxxxxxx> <20060630081420.A1371683@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.11+cvs20060403
* Nathan Scott <nathans@xxxxxxx>:
> 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

<Prev in Thread] Current Thread [Next in Thread>