xfs
[Top] [All Lists]

Re: XFS hang during xfs_fsr run

To: Michael Weissenbacher <mw@xxxxxxxxxxxx>
Subject: Re: XFS hang during xfs_fsr run
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 08 Mar 2010 12:09:03 -0600
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <4B94EADD.2080108@xxxxxxxxxxxx>
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> <4B94EADD.2080108@xxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
Michael Weissenbacher wrote:
> 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?

Odds are you'll still oops, just earlier.  Send anything interesting
you see in the dmesg if/when it happens...

-Eric
 
> thanks,
> Michael
> 
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
> 

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