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

While performing the lookup on EC volume, lots of following errors were reported in the brick logs:

[2017-07-18 16:13:47.594241] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"
[2017-07-18 16:13:47.617064] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"
[2017-07-18 16:13:47.618151] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"
[2017-07-18 16:13:48.680307] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"
[2017-07-18 16:13:48.680831] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"
[2017-07-18 16:13:48.707445] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"
[2017-07-18 16:13:48.707959] E [inode.c:954:__inode_link] (-->/usr/lib64/glusterfs/3.8.4/xlator/features/quota.so(+0x15895) [0x7fa0e4b07895] -->/lib64/libglusterfs.so.0(inode_link+0x39) [0x7fa0f53fd809] -->/lib64/libglusterfs.so.0(+0x394a9) [0x7fa0f53fd4a9] ) 0-: Assertion failed: !"link attempted on non-directory parent"

I havent seen any functionality impact yet, however following is the outcome of the discussion with sanoj

"Functionality imapct.. writes on such hard link files would not get propagated up to root immediately. (but would happen eventually as the directory containing has a lookup).. It is a rare case that a directory has a file with hardlink to another file in same directory"


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

glusterfs-3.8.4-18.5.el7rhgs.x86_64


How reproducible:
=================

Have to retry another time. 

Steps carried:
==============

The steps carried were in geo-rep setup, however the logs on master bricks. Providing only the steps that is needed to avoid confusion. 

1. Create 6 node Master Cluster
2. Create EC volume on Master (2x(4+2)). Enable quota. 
3. Mount the volume (Fuse)
4. Using crefi, create the data set. fops carried inorder were:

create, chmod, chown, chgrp, hardlink, symlink, truncate

5. After every fop, calculate the checksum of mount (At least twice)
6. After truncate, checksum never matched

Actual results:
===============

Assertion failed: !"link attempted on non-directory parent"