Bug 1121186

Description of problem:
=======================
when Directory deletion is in progress (completed on all or few non hashed sub-volume and not on hashed sub-volumes) and lookup comes from another mount point it heals Directory everywhere.(on non hashed sub-volumes from where it was deleted) After that deletion its parent fails with an error 'Directory not empty' and on listing parents content child Directory is not shown on mount as it is not healed on hashed sub-volume



Version-Release number :
=========================
3.6.0.24-1.el6rhs.x86_64


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


Steps to Reproduce:
====================
1. create and mount distributed volume. (mount on multiple client)
2. Directories on mount point.
[root@OVM1 gdb1]# mkdir -p 1/2/3

backend:-
[root@OVM3 ~]# tree  /var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick*/*/gdb1/ 
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick1/r1/gdb1/
└── 1
    └── 2
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick2/r2/gdb1/
└── 1
    └── 2
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick3/r3/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick4/r4/gdb1/
└── 1
    └── 2
        └── 3
3. from one mount point execute 'rm -rf *' and from other mount point send lookup when Directory is not removed from hashed and removed from other sub-volume

-->mount1:-
[root@OVM1 gdb1]# rm -rf *

bricks:-
[root@OVM3 ~]# tree  /var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick*/*/gdb1/ 
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick1/r1/gdb1/
└── 1
    └── 2
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick2/r2/gdb1/
└── 1
    └── 2
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick3/r3/gdb1/
└── 1
    └── 2
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick4/r4/gdb1/
└── 1
    └── 2
        └── 3

---> send look up now
mount 2:-
[root@OVM1 gdb1]# ls -lR

[root@OVM3 ~]# tree  /var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick*/*/gdb1/ 
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick1/r1/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick2/r2/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick3/r3/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick4/r4/gdb1/
└── 1
    └── 2
        └── 3

12 directories, 0 files

----> rm will fail on first mount:-

[root@OVM1 gdb1]# rm -rf *
rm: cannot remove `1/2': Directory not empty

mount:-
[root@OVM1 gdb1]# ls -lR
.:
total 0
drwxr-xr-x 3 root root 70 Jul 18 14:21 1

./1:
total 0
drwxr-xr-x 2 root root 54 Jul 18 14:23 2

./1/2:
total 0
<----------------------------- directory is not listed here but present in all non-hashed bricks

bricks:-
[root@OVM3 ~]# tree  /var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick*/*/gdb1/ 
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick1/r1/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick2/r2/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick3/r3/gdb1/
└── 1
    └── 2
        └── 3
/var/run/gluster/snaps/c8189009534a45aa85a0c66928498dca/brick4/r4/gdb1/
└── 1
    └── 2

11 directories, 0 files






Actual results:
===============
- Directory deletion fails with error 'not empty' but mount point did not show any Dir/files inside it


Expected results:
=================
Directory deletion should not fail with this error
- no two directories should have same gfid