[lkml]   [2009]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: nfsd: page allocation failure - nfsd or kernel problem?
Michael Tokarev napsal(a):
> J. Bruce Fields wrote:
>> 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 ?
>>>>> 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
> Note the NOT, in upper case ;)
>>> 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:
> Does not look similar.
> I repeated the issue here. The slab which is growing here is buffer_head.
> It's growing slowly -- right now, after ~5 minutes of constant writes over
> nfs, its size is 428423 objects, growing at about 5000 objects/minute rate.
> When stopping writing, the cache shrinks slowly back to an acceptable
> size, probably when the data gets actually written to disk.
> It looks like we need a bug entry for this :)
> I'll re-try 2.6.30 hopefully tomorrow.
> /mjt

Can you try if increasing vm.min_free_kbytes will help you? I
"temp-fixed" heavy I/O problems with vm.min_free_kbytes=32768 on machine
with 4G memory.


 \ /
  Last update: 2009-06-18 02:23    [W:0.090 / U:3.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site