[Bugs] [Bug 1217372] New: Disperse volume: NFS client mount point hung after the bricks came back up

[bugzilla at redhat.com]

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

            Bug ID: 1217372
           Summary: Disperse volume: NFS client mount point hung after the
                    bricks came back up
           Product: GlusterFS
           Version: mainline
         Component: disperse
          Assignee: bugs at gluster.org
          Reporter: byarlaga at redhat.com
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Created attachment 1020467
  --> https://bugzilla.redhat.com/attachment.cgi?id=1020467&action=edit
NFS process statedump

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

client mount and IO hung after the bricks came back up with gluster v start
force.
This is seen with the pathch for ec heal sent by pranith

Version-Release number of selected component (if applicable):
============================================================
[root at ninja ~]# 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. NFS mount a distributed disperse volume on a client
2. Run IO, creating directories and files
3. Bring down 2 of the bricks and start the volume with force options after
some time and check the client mount and IO

Actual results:


Expected results:


Additional info:
================
Attaching the nfs process statedump.

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