All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.29.1: nfsd: page allocation failure - nfsd or kernel problem?
Date: Wed, 17 Jun 2009 12:43:44 +0400	[thread overview]
Message-ID: <4A38ACC0.3060501@msgid.tls.msk.ru> (raw)
In-Reply-To: <4A37FE48.6070306@msgid.tls.msk.ru>

Michael Tokarev wrote:
> Justin Piszcz wrote:
>> Package: nfs-kernel-server
>> Version: 1.1.6-1
>> Distribution: Debian Testing
>> Architecture: 64-bit
>>
>> [6042655.755870] Pid: 7093, comm: nfsd Not tainted 2.6.29.1 #4
>> [6042655.755872] Call Trace:
>> [6042655.755874]  <IRQ>  [<ffffffff802850fd>]  
>> __alloc_pages_internal+0x3dd/0x4e0
>> [6042655.755885]  [<ffffffff802a738b>] cache_alloc_refill+0x2fb/0x570
>> [6042655.755887]  [<ffffffff802a76db>] __kmalloc+0xdb/0xe0
> 
> Was about to send this same report.
> 
> The thing continues servicing files it seems, but after some quite
> good delay.
> 
> This happens after massive amount of writes.  2.6.29.4 does the
> same thing.  Here it is, for comparison:
> 
> Jun 13 17:06:42 gnome vmunix: nfsd: page allocation failure. order:0, mode:0x20
> Jun 13 17:06:42 gnome vmunix: Call Trace:
> Jun 13 17:06:42 gnome vmunix:  <IRQ>  [<ffffffff8029559d>]  __alloc_pages_internal+0x3fd/0x500
> Jun 13 17:06:42 gnome vmunix:  [<ffffffff802bd4c3>]  cache_alloc_refill+0x313/0x5c0
> Jun 13 17:06:42 gnome vmunix:  [<ffffffff802bd873>] __kmalloc+0x103/0x110
> Jun 13 17:06:42 gnome vmunix:  [<ffffffff803dca6d>] __alloc_skb+0x6d/0x150
...

Justin, by the way, what's the underlying filesystem on the server?

I've seen this error on 2 machines already (both running 2.6.29.x x86-64),
and in both cases the filesystem on the server was xfs.  May this be
related somehow to http://bugzilla.kernel.org/show_bug.cgi?id=13375 ?
That one is different, but also about xfs and nfs.  I'm trying to
reproduce the problem on different filesystem...

/mjt

  reply	other threads:[~2009-06-17  8:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.00.0906161203160.27742@p34.internal.lan>
2009-06-16 16:06 ` 2.6.29.1: nfsd: page allocation failure - nfsd or kernel problem? Justin Piszcz
2009-06-16 20:19   ` Michael Tokarev
2009-06-17  8:43     ` Michael Tokarev [this message]
2009-06-17  9:43       ` Justin Piszcz
2009-06-17 10:39         ` Michael Tokarev
2009-06-17 18:51           ` J. Bruce Fields
2009-06-17 20:24             ` Michael Tokarev
2009-06-17 20:39               ` David Rientjes
2009-06-18  8:54                 ` Michael Tokarev
2009-06-18 17:07                   ` David Rientjes
2009-06-18 17:56                     ` Michael Tokarev
2009-06-18 18:12                       ` J. Bruce Fields
2009-06-18 18:15                       ` David Rientjes
2009-06-17 22:45               ` J. Bruce Fields
2009-06-18  0:14               ` Zdenek Kaspar
2009-06-17 19:44   ` [patch] ipv4: don't warn about skb ack allocation failures David Rientjes
2009-06-17 20:16     ` Eric Dumazet
2009-06-17 20:33       ` David Rientjes
2009-06-17 20:52         ` Eric Dumazet
2009-06-17 21:12           ` David Rientjes
2009-06-17 22:30             ` Eric Dumazet
2009-06-17 23:08               ` David Miller
2009-06-18 16:56                 ` David Rientjes
2009-06-18 19:00                   ` David Miller
2009-06-18 19:23                     ` David Rientjes
2009-06-18 19:37                       ` David Miller
2009-06-19 19:45                         ` David Rientjes
2009-06-19 20:41                         ` Eric W. Biederman
2009-06-19 22:37                           ` David Rientjes
2009-06-19 23:04                             ` David Miller
2009-06-20  1:28                             ` Eric W. Biederman
2009-06-19 23:03                           ` David Miller
2009-06-22 16:08 ` 2.6.30: nfsd: page allocation failure - nfsd or kernel problem? (again with 2.6.30) Justin Piszcz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A38ACC0.3060501@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.