As discussed, the issue wasn't reproduced on setup with 4node samba and 4 clients when ctdb was added. The issue originally was reported with samba cluster but no ctdb which is not a valid setup. Hence deferring it from 3.3. But would like to retain the BZ and see if there is any other bug that is being exposed only in non CTDB setup as the same was working earlier.
Created attachment 1293899 [details] screen shot
Hi Karan, I looked over the from comment #9. It's weird that I am not seeing any 'Permission denied' or related errors in any of the logs(samba/glusterfs-client/brick logs). Since you mentioned it as 100% reproducible, can you please make the following changes to /etc/samba/smb.conf and re-run the tests in hope of getting some useful logs. * Change 'max log size = 50' --> 'max log size = 0' * Add 'log level = 7' * And in [glusterfs-<VOLNAME>] section change 'glusterfs:loglevel = 7' --> 'glusterfs:loglevel = 8' Additionally, you can also increase the brick log level to DEBUG.
Upstream patches: https://review.gluster.org/#/c/17956/ https://review.gluster.org/#/c/17910/
(In reply to Poornima G from comment #18) > Upstream patches: https://review.gluster.org/#/c/17910/ https://review.gluster.org/#/c/17967
(In reply to Poornima G from comment #20) > (In reply to Poornima G from comment #18) > > Upstream patches: > > https://review.gluster.org/#/c/17910/ 17910 will not be pulled into downstream. > https://review.gluster.org/#/c/17967
release-3.12 patch : https://review.gluster.org/#/c/18001/ downstream patch : https://code.engineering.redhat.com/gerrit/#/c/114763/
https://review.gluster.org/#/c/17910/ is not really related to this bug, hence deferring that patch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2774