On Sat, Jun 24, 2017 at 3:17 PM, Abi Askushi <rightkicktech@gmail.com> wrote:
Hi all,

For the records, I had to remove manually the conflicting directory and ts respective gfid from the arbiter volume:

 getfattr -m . -d -e hex e1c80750-b880-495e-9609-b8bc7760d101/ha_agent

That gave me the gfid: 0x277c9caa9dce4a17a2a93775357befd5

Then cd .glusterfs/27/7c

rm -rf 277c9caa-9dce-4a17-a2a9-3775357befd5 (or move it out of there)

Triggerred heal: gluster volume heal engine

Then all ok:

gluster volume heal engine info
Brick gluster0:/gluster/engine/brick
Status: Connected
Number of entries: 0

Brick gluster1:/gluster/engine/brick
Status: Connected
Number of entries: 0

Brick gluster2:/gluster/engine/brick
Status: Connected
Number of entries: 0

Thanx. 

​Hi Abi,

What is the volume type of 'engine' volume ?
Could you also provide the output of 'gluster volume info engine' to get to the
closer look at the problem

​-- sas​