Run glusterfs untar on 1 client, and rm -rf in loop on another client.

After stopping rm, stop untar. Then rm -rf the dir leads to the error.

root@shishirng:/mnt/dht# rm -rf glusterfs-3.2.5qa4
rm: cannot remove `glusterfs-3.2.5qa4/rpc/rpc-transport/rdma': Directory not empty
rm: cannot remove `glusterfs-3.2.5qa4/rpc/rpc-transport/socket': Directory not empty

The problem is in the backend, firs_up_subvol has missing dirents.
gfid's, and layout's of dirs existing on both bricks are fine.

But dirents present in only 1 brick have layout set to:

root@shishirng:/gluster/glusterfs# getfattr --dump -e hex -m trusted /export/dir{3,4}/glus*/rpc/rpc-transport/rdma/src
getfattr: /export/dir3/glus*/rpc/rpc-transport/rdma/src: No such file or directory
getfattr: Removing leading '/' from absolute path names
# file: export/dir4/glusterfs-3.2.5qa4/rpc/rpc-transport/rdma/src
trusted.gfid=0x7428ed99658b4627b8856cf26b752d32
trusted.glusterfs.dht=0x000000010000000000000000ffffffff <-----