kernel-packages team mailing list archive

[Dave Chiluk <1047566@xxxxxxxxxxxxxxxxxx>]

I could not reproduce this problem, and will need some sort of
reproduction procedure in order to pursue it further.

I created a filesystem with 680666 randomly named 4k files,  spread out
among 6811 nested directories at a max depth of 5 levels of directories.

I exported the filesystem using the following options 
/nfs      192.168.122.1/24(rw,no_root_squash,no_subtree_check,async)

And mounted it with the following mount options.
(rw,vers=4,addr=192.168.122.186,clientaddr=192.168.122.115)

I then spawned 10 threads on the client running
<<<<<<<<<<<<<<<<<<<<<<<< 
#!/bin/bash
find ./ -type f | while read line 
do
        cat $line > /dev/null
done
>>>>>>>>>>>>>>>>>>>>>>>>

I could not get the idr_layer_cache to increase above 890k.   I am
running the following kernel- 3.2.0-53-virtual.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1047566

Title:
  Memory leaks when using NFS

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When using Ubuntu Server 12.04 with or without the latest updates
  (kernels 3.2.0-23 and 3.2.0-29, x86_64) as an NFS server with fairly
  heavy reading activity from clients (no writing), from a volume with a
  lot of small files, split into many subdirectories (with about 5-10
  files or subdirectories per directory, in a tree-like structure not
  unlike that of Squid proxy), available memory is quickly exhausted,
  however no single process shows that much memory being used, nor does
  the "buffers" or "cached" in "free" command output. The server
  eventually runs out of memory and crashes.

  slabtop shows that majority of memory is being used by idr_layer_cache
  (3.6G on a sever with 4G of RAM shortly before the kernel started
  killing processes and eventually crashed).

  The filesystem being shared is ext4. Clients (also the same version of
  Ubuntu Server) mount the volume in read-only mode, with default
  options.

  P.S. Also tried i386 version, with the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1047566/+subscriptions