xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: XFS hang during xfs_fsr run

from [Michael Weissenbacher] [Permanent Link][Original]
To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: XFS hang during xfs_fsr run
From: Michael Weissenbacher <mw@xxxxxxxxxxxx>
Date: Mon, 08 Mar 2010 13:17:33 +0100
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20100308000601.GF28189@xxxxxxxxxxxxxxxx>
References: <4B8F871C.60802@xxxxxxxxxxxx> <20100304112018.GG14317@xxxxxxxxxxxxxxxx> <4B8FA2CD.6010904@xxxxxxxxxxxx> <20100304131511.GH14317@xxxxxxxxxxxxxxxx> <20100304134641.GA26871@xxxxxxxxxxxxx> <4B8FC1B7.3070505@xxxxxxxxxxxx> <20100304222611.GK14317@xxxxxxxxxxxxxxxx> <4B92C71C.5010003@xxxxxxxxxxxx> <20100308000601.GF28189@xxxxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.23 (X11/20090817) 
Hi Dave!

That's ... unexpected. That implies that ip->i_temp == NULL after it
has been joined to a transaction. I can't see how that could occur
there.  Can you recompile the kernel with CONFIG_XFS_DEBUG and
re-run the test as that option includes all sorts of sanity checks
for ip->i_temp?
CONFIG_XFS_DEBUG is enabled now. Is there anything special in dmesg i should look for? Or should i just send another oops when it happens again? 

thanks,
Michael
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: xfs: add fs name to kthreads, Dave Chinner
Next by Date:  [PATCH, RFC] xfs: add discard support, Christoph Hellwig
Previous by Thread:  Re: XFS hang during xfs_fsr run, Dave Chinner
Next by Thread:  Re: XFS hang during xfs_fsr run, Eric Sandeen
Indexes:  [Date] [Thread] [Top] [All Lists]