We're still having issues with higher-order allocations failing and
triggering an OOM kill for unexplainable reasons. (on 4.4.0-78-generic).
I've attached the relevant OOM killer logs. It may be relevant to note
that the server these logs are from is an Elasticsearch instance with a
large (~32GB)
I can confirm this problem on Precise 12.04.3 with mountall=2.36.4 from
precise-updates.
With clientaddr=0.0.0.0, nfsstat -s showed rapidly incrementing
'setcltid' and 'setcltidconf' operations on the server, and high IO
utilization on the root volume due to writing v4recovery information.
