[Top] [All Lists]

Re: XFS hang during xfs_fsr run

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 (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?


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