xfs
[Top] [All Lists]

Re: Excessive xfs_inode allocations trigger OOM killer

To: Michal Hocko <mhocko@xxxxxxxxxx>
Subject: Re: Excessive xfs_inode allocations trigger OOM killer
From: Florian Weimer <fw@xxxxxxxxxxxxx>
Date: Mon, 03 Oct 2016 19:35:18 +0200
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160926200209.GA23827@xxxxxxxxxxxxxx> (Michal Hocko's message of "Mon, 26 Sep 2016 22:02:10 +0200")
References: <87a8f2pd2d.fsf@xxxxxxxxxxxxxxxxx> <20160920203039.GI340@dastard> <87mvj2mgsg.fsf@xxxxxxxxxxxxxxxxx> <20160920214612.GJ340@dastard> <20160921080425.GC10300@xxxxxxxxxxxxxx> <878tuetvl6.fsf@xxxxxxxxxxxxxxxxx> <20160926200209.GA23827@xxxxxxxxxxxxxx>
* Michal Hocko:

>> I'm not sure if I can reproduce this issue in a sufficiently reliable
>> way, but I can try.  (I still have not found the process which causes
>> the xfs_inode allocations go up.)
>> 
>> Is linux-next still the tree to test?
>
> Yes it contains all the compaction related fixes which we believe to
> address recent higher order OOMs.

I tried 4.7.5 instead.  I could not reproduce the issue so far there.
Thanks to whoever fixed it. :)

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