| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS / writeback invoking soft lockup. |
| From: | Dave Jones <davej@xxxxxxxxxx> |
| Date: | Fri, 13 Dec 2013 11:22:28 -0500 |
| Cc: | Dave Chinner <david@xxxxxxxxxxxxx>, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20131213111639.GD23546@xxxxxxxxxxxxx> |
| Mail-followup-to: | Dave Jones <davej@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <20131213071407.GA6527@xxxxxxxxxx> <20131213104853.GS10988@dastard> <20131213111639.GD23546@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Dec 13, 2013 at 03:16:39AM -0800, Christoph Hellwig wrote:
> On Fri, Dec 13, 2013 at 09:48:53PM +1100, Dave Chinner wrote:
> > All I can say is that there doesn't look to be any obvious signs
> > that this is a XFS or writeback problem fom the stack trace, and
> > without more information or a reproducable test case I'm not going
> > to be able to understand the cause.
> >
> > Is the problem reproducable, or is it just a one-off?
>
> If it's reproducable it would be good to enable the xfs_writepage
> tracepoint and get a trace-cmd log of it.
I hit it pretty reliably last night. I'll make a note to look into it
on monday with that enabled.
Dave
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 5/5] xfs: allow linkat() on O_TMPFILE files, Zhi Yong Wu |
|---|---|
| Next by Date: | [PATCH 5/3] xfs: return unlocked dquots from xfs_qm_dqqet, Christoph Hellwig |
| Previous by Thread: | Re: XFS / writeback invoking soft lockup., Christoph Hellwig |
| Next by Thread: | Re: XFS / writeback invoking soft lockup., Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |