+++ This bug was initially created as a clone of Bug #1338634 +++
+++ This bug was initially created as a clone of Bug #1286582 +++
+++ This bug was initially created as a clone of Bug #986916 +++
Description of problem:
In a distribute-replicate volume, when directories with same names are created and deleted continuously on fuse and nfs mount points, after certain time the mount points hang.
dir=$(dirname $(readlink -f $0))
echo 'Script in '$dir
mkdir -p foo$1/bar/gee
mkdir -p foo$1/bar/gne
mkdir -p foo$1/lna/gme
rm -rf foo$1
Steps to Reproduce:
1. Create a distribute-replicate volume ( 6 x 2 ). 4 storage nodes . 3 bricks on each storage node.
2. Start the volume.
3. Create 2 fuse and 2 nfs mounts on each RHEL5.9 and RHEL6.4 clients.
4. From all the mount points execute: "test_bug_922792.sh"
After sometime, fuse and nfs mount hangs.
Fuse and nfs mount shouldn't hang.
--- Additional comment from Vijay Bellur on 2016-05-23 04:32:17 EDT ---
REVIEW: http://review.gluster.org/14496 (dht: selfheal should wind mkdir call to subvols with ESTALE error) posted (#1) for review on master by Sakshi Bansal
REVIEW: http://review.gluster.org/14500 (dht: selfheal should wind mkdir call to subvols with ESTALE error) posted (#1) for review on release-3.8 by Sakshi Bansal
COMMIT: http://review.gluster.org/14500 committed in release-3.8 by Raghavendra G (firstname.lastname@example.org)
Author: Sakshi Bansal <email@example.com>
Date: Fri May 20 15:16:17 2016 +0530
dht: selfheal should wind mkdir call to subvols with ESTALE error
Backport of http://review.gluster.org/#/c/14496/
> Change-Id: I7140e50263b5f28b900829592c664fa1d79f3f99
> BUG: 1338634
> Signed-off-by: Sakshi Bansal <firstname.lastname@example.org>
Signed-off-by: Sakshi Bansal <email@example.com>
NetBSD-regression: NetBSD Build System <firstname.lastname@example.org>
CentOS-regression: Gluster Build System <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Raghavendra G <email@example.com>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.