From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.29.1: nfsd: page allocation failure - nfsd or kernel problem?
Date: Wed, 17 Jun 2009 14:51:39 -0400 [thread overview]
Message-ID: <20090617185139.GF24040@fieldses.org> (raw)
In-Reply-To: <4A38C7CA.7040005@msgid.tls.msk.ru>
On Wed, Jun 17, 2009 at 02:39:06PM +0400, Michael Tokarev wrote:
> Justin Piszcz wrote:
>>
>>
>> On Wed, 17 Jun 2009, Michael Tokarev wrote:
>>
>>> Michael Tokarev wrote:
>>>> Justin Piszcz wrote:
>>> ...
>>>
>>> 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...
>>
>> Hello, I am also running XFS on 2.6.29.x x86-64.
>>
>> For me, the error happened when I was running an XFSDUMP from a client
>> (and dumping) the stream over NFS to the XFS server/filesystem. This
>> is typically when the error occurs or during heavy I/O.
>
> Very similar load was here -- not xfsdump but tar and dump of an ext3
> filesystems.
>
> And no, it's NOT xfs-related: I can trigger the same issue easily on
> ext4 as well. About 20 minutes of running 'dump' of another fs
> to the nfs mount and voila, nfs server reports the same page allocation
> failure. Note that all file operations are still working, i.e. it
> produces good (not corrupted) files on the server.
There's a possibly related report for 2.6.30 here:
http://bugzilla.kernel.org/show_bug.cgi?id=13518
--b.
next prev parent reply other threads:[~2009-06-17 18:51 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
2009-06-17 9:43 ` Justin Piszcz
2009-06-17 10:39 ` Michael Tokarev
2009-06-17 18:51 ` J. Bruce Fields [this message]
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=20090617185139.GF24040@fieldses.org \
--to=bfields@fieldses.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox