Description of problem: ****************************** When multiple files are created from one of the cifs mount and are renamed in loop, executing ll on that renamed file from another cifs mount succeeds even when the file is already renamed.chmod also succeeded on that file. For ex. : From mnt1: create file1 from cifs mnt1 rename it to f1 From mnt2: ll file1 chmod 766 file1 Above operations succeeds from mnt2 On mnt1 : ll file1: no such file or directory Version-Release number of selected component (if applicable): glusterfs-libs-3.8.2-0.24.gitf524648.el7.x86_64 glusterfs-debuginfo-3.8.2-0.24.gitf524648.el7.x86_64 glusterfs-cli-3.8.2-0.24.gitf524648.el7.x86_64 glusterfs-3.8.2-0.24.gitf524648.el7.x86_64 glusterfs-server-3.8.2-0.24.gitf524648.el7.x86_64 samba-vfs-glusterfs-4.4.5-1.el7rhgs.x86_64 glusterfs-fuse-3.8.2-0.24.gitf524648.el7.x86_64 glusterfs-api-3.8.2-0.24.gitf524648.el7.x86_64 glusterfs-client-xlators-3.8.2-0.24.gitf524648.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Multiple cifs mount 2.Create 10 files from mnt1 3.Rename 10 files in loop from mnt1 4.ll of file1 from mnt2 5. chmod 776 file1 Actual results: the listing and chmod succeeds from one of the mount points for the file which is already renamed from another mount point. Expected results: the other cifs client should get updated with the renamed file name and should not list or allow any operation on the old filename. Additional info:
All 3.8.x bugs are now reported against version 3.8 (without .x). For more information, see http://www.gluster.org/pipermail/gluster-devel/2016-September/050859.html
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.