[Bugs] [Bug 1218488] New: Brick and nfs processes gets killed with OOM

bugzilla at redhat.com bugzilla at redhat.com
Tue May 5 05:13:22 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1218488

            Bug ID: 1218488
           Summary: Brick and nfs processes gets killed with OOM
           Product: GlusterFS
           Version: mainline
         Component: nfs
          Assignee: bugs at gluster.org
          Reporter: byarlaga at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
=======================

distributed disperse EC volume (2x(8+4) is nfs mounted on client. IO (plain
directory creation and files creation) is run from client. There are around
100000 directories and 10000 files existing already and data is added. Did 'ls'
on the directory to list and the mount hangs. The sequence of events that are
happening are :

1. mount process hangs
2. bricks crash
3. NFS server doesn't respond
4. rpcinfo doesn't show the volume export
5. NFS server crashes with OOM

This is being tested on master with pranith's patches related to heal applied.

Version-Release number of selected component (if applicable):
============================================================
[root at vertigo bricks]# gluster --version
glusterfs 3.8dev built on Apr 30 2015 11:14:47
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.

How reproducible:
=================
100%

Steps to Reproduce:
1. Create a 2x(8+4) ec volume and nfs mount on the client
2. create around 200k directories and 10k files
3. do a 'ls' on the directories to list.

Actual results:
===============
Client mount hung and bricks and nfs servers crashed with OOM.

Expected results:


Additional info:
sosreports will be copied to rhsqe-repo:/sosreports/<bugid>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list