Bug 1537065

Description of problem:
[root@apandey dir]# getfattr -n trusted.ec.heal  file
file: trusted.ec.heal: Transport endpoint is not connected
[root@apandey dir]# getfattr -n trusted.ec.heal  file
# file: file
trusted.ec.heal="Good: 000000, Bad: 111111"

[root@apandey dir]# 


Version-Release number of selected component (if applicable):



[root@apandey dir]# glusterfs --version
glusterfs 4.0dev1
Repository revision: git://git.gluster.org/glusterfs.git
Copyright (c) 2006-2016 Red Hat, Inc. <https://www.gluster.org/>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
It is licensed to you under your choice of the GNU Lesser
General Public License, version 3 or any later version (LGPLv3
or later), or the GNU General Public License, version 2 (GPLv2),
in all cases as published by the Free Software Foundation.
[root@apandey dir]# 


How reproducible:
100%

Steps to Reproduce:
1. create 4+2 ec volume and mount it
2. create a file mount point
3. Go to one of the brick from backend and delete file from real path and also from .glusterfs/folder

4 - trigger client side heal by following command -
getfattr -n trusted.ec.heal  file
IN first attempt is shows error 
file: trusted.ec.heal: Transport endpoint is not connected
However heal get triggered.

In next attempt it shows wrong Good and Bad values

Actual results:
Error and wrong status of volume.

Expected results:
client side heal work without error and should give correct status.

Additional info: