| To: | Nathan Scott <nathans@xxxxxxx> |
|---|---|
| Subject: | Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4 |
| From: | Timothy Shimmin <tes@xxxxxxx> |
| Date: | Fri, 30 Jun 2006 15:35:40 +1000 |
| Cc: | Ralf Hildebrandt <Ralf.Hildebrandt@xxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <20060630081420.A1371683@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Organization: | SGI |
| References: | <20060629203809.GD20456@xxxxxxxxxx> <20060630081420.A1371683@xxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.8.2 |
On Friday 30 June 2006 8:14 am, Nathan Scott wrote: > 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?). Tim, do you see any situation > in recovery where we might have freed an inode while it was locked? Had a look but I can't see anything apparent at this stage, let's run our unlink recovery test on the -mm tree next week, which should expose the bug. --Tim |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4, Nathan Scott |
|---|---|
| Next by Date: | Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4, Ralf Hildebrandt |
| Previous by Thread: | Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4, Nathan Scott |
| Next by Thread: | Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4, Ralf Hildebrandt |
| Indexes: | [Date] [Thread] [Top] [All Lists] |