| To: | Dave Jones <davej@xxxxxxxxxx>, xfs@xxxxxxxxxxx, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-mm@xxxxxxxxx |
|---|---|
| Subject: | Re: XFS WARN_ON in xfs_vm_writepage |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 19 Jun 2014 12:03:40 +1000 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20140613141925.GA24199@xxxxxxxxxx> |
| References: | <20140613051631.GA9394@xxxxxxxxxx> <20140613062645.GZ9508@dastard> <20140613141925.GA24199@xxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Jun 13, 2014 at 10:19:25AM -0400, Dave Jones wrote: > 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. Yup, sounds like a problem somewhere in mm/vmscan.c.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: log record CRC mismatch: found 0x10a71f1d, expected 0xe012d25f, Dave Chinner |
|---|---|
| Next by Date: | Re: xfs_repair issue with ACLs on v5 XFS when beyond v4 limits, Dave Chinner |
| Previous by Thread: | Re: XFS WARN_ON in xfs_vm_writepage, Dave Jones |
| Next by Thread: | Re: XFS WARN_ON in xfs_vm_writepage, Dave Jones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |