Return-Path: linux-nfs-owner@vger.kernel.org Received: from mail-vc0-f178.google.com ([209.85.220.178]:62265 "EHLO mail-vc0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752808AbaGJUIc convert rfc822-to-8bit (ORCPT ); Thu, 10 Jul 2014 16:08:32 -0400 Received: by mail-vc0-f178.google.com with SMTP id ij19so211249vcb.9 for ; Thu, 10 Jul 2014 13:08:31 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1FAA3C78-BBFA-4186-A25A-0D4E97609934@netapp.com> References: <1FAA3C78-BBFA-4186-A25A-0D4E97609934@netapp.com> Date: Thu, 10 Jul 2014 16:08:31 -0400 Message-ID: Subject: Re: rpciod/1: page allocation failure. order:2, mode:0x20' From: Trond Myklebust To: "Adamson, Andy" Cc: NFS list Content-Type: text/plain; charset=UTF-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Thu, Jul 10, 2014 at 4:01 PM, Adamson, Andy wrote: > Hi > > A customer of ours, running a 2.6.32-431.5.1.el6.x86_64 kernel NFS client, is hittng the "rpciod/1: page allocation failure. order:2, mode:0x20", but only with NFSv3 hard mounts (not soft mounts), and not with NFSv4 (same application, same client hardware). Has anyone hit this issue with RHEL6.5? Any ideas on why NFSv3 would trigger this error and not NFSv4? > > I see in Red Hat Bugzilla 767127 - swapper: page allocation failure. order:1, mode:0x20 (edit) that a similar issue was solved by setting vm.zone_reclaim_mode = 1 which used to be the default. Adjusting the vm.min_free_kbytes higher may also help. Any side effects or issues with these settings? > > Any info appreciated Where are we doing an order 2 allocation in the NFS/RPC code? Our aim has always been to do nothing larger than an order 0 allocation. -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@primarydata.com