| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS WARN_ON in xfs_vm_writepage |
| From: | Dave Jones <davej@xxxxxxxxxx> |
| Date: | Fri, 13 Jun 2014 10:19:25 -0400 |
| Cc: | xfs@xxxxxxxxxxx, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140613062645.GZ9508@dastard> |
| Mail-followup-to: | Dave Jones <davej@xxxxxxxxxx>, Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx |
| References: | <20140613051631.GA9394@xxxxxxxxxx> <20140613062645.GZ9508@dastard> |
| User-agent: | Mutt/1.5.23 (2014-03-12) |
On Fri, Jun 13, 2014 at 04:26:45PM +1000, Dave Chinner wrote:
> > 970 if (WARN_ON_ONCE((current->flags & (PF_MEMALLOC|PF_KSWAPD)) ==
> > 971 PF_MEMALLOC))
>
> What were you running at the time? The XFS warning is there to
> indicate that memory reclaim is doing something it shouldn't (i.e.
> dirty page writeback from direct reclaim), so this is one for the mm
> folk to work out...
Trinity had driven the machine deeply into swap, and the oom killer was
kicking in pretty often. Then this happened.
Dave
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: how to locate the file through blktrace with xfs, Brian Foster |
|---|---|
| Next by Date: | Re: (Un)known issue with XFS group quotas on LVM?, John Desantis |
| Previous by Thread: | Re: XFS WARN_ON in xfs_vm_writepage, Dave Chinner |
| Next by Thread: | Re: XFS WARN_ON in xfs_vm_writepage, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |