[Bugs] [Bug 1549915] [Fuse Sub-dir] After performing add-brick on volume, doing rm -rf * on subdir mount point fails with " Transport endpoint is not connected"

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1549915



--- Comment #1 from Amar Tumballi <atumball at redhat.com> ---
Description of problem:

While sub-dir is mounted on client and add-brick is performed,doing rm -rf * on
mount point fails to delete the directories present on mount point 



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

How reproducible:
2/2

Steps to Reproduce:
1.Create 3 x (2 + 1) = 9 Arbiter volume.
2.Mount the volume on client via Fuse
3.Create a directory say "dir1" inside the mount point
4.Set permissions for the directory on volume 
# gluster v set glustervol auth.allow "/dir1(10.70.37.192)"
volume set: success

5.Mount the sub-dir "dir1" on client.
 mount -t glusterfs node1:glustervol/dir1 /mnt/posix_Parent/

5.Create 1000 directories on mount point

6.Perform add brick 
# gluster v add-brick glustervol node1:/gluster/brick3/3
node2:/gluster/brick3/3 node3:/gluster/brick3/3 
volume add-brick: success

7.After performing add-brick,do rm -rf * on mount point




Actual results:

rm -rf * on mount point results in "Transport endpoint is not connected".Even
though the subdir is mounted on client.

rm: cannot remove ‘sd979’: Transport endpoint is not connected
rm: cannot remove ‘sd98’: Transport endpoint is not connected
rm: cannot remove ‘sd980’: Transport endpoint is not connected
rm: cannot remove ‘sd981’: Transport endpoint is not connected
rm: cannot remove ‘sd982’: Transport endpoint is not connected
rm: cannot remove ‘sd983’: Transport endpoint is not connected
rm: cannot remove ‘sd984’: Transport endpoint is not connected
rm: cannot remove ‘sd985’: Transport endpoint is not connected
rm: cannot remove ‘sd986’: Transport endpoint is not connected

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.