https://code.engineering.redhat.com/gerrit/#/c/124/
Patch posted for review at https://code.engineering.redhat.com/gerrit/14241 - rhs-2.1-u1 branch https://code.engineering.redhat.com/gerrit/14240 - rhs-2.1 branch
Tested with glusterfs-server-3.4.0.36rhs-1.el6rhs.x86_64, Created two volumes named dis-rep1, dis-rep12, started these volumes multiple times with force as below. There is only single entry for each volume in smb.conf. Hence marking the bug as verfied. [root@bvt-rhs1 .unsupported]# gluster v start dis-rep12 force volume start: dis-rep12: success [root@bvt-rhs1 .unsupported]# gluster v start dis-rep12 force volume start: dis-rep12: success [ [root@bvt-rhs1 .unsupported]# gluster v start dis-rep1 force volume start: dis-rep1: success [root@bvt-rhs1 .unsupported]# gluster v start dis-rep1 force less /etc/samba/smb.conf [gluster-dis-rep1] comment = For samba share of volume dis-rep1 vfs objects = glusterfs glusterfs:volume = dis-rep1 glusterfs:logfile = /var/log/samba/glusterfs-dis-rep1.log glusterfs:loglevel = 7 path = / read only = no guest ok = yes [gluster-dis-rep12] comment = For samba share of volume dis-rep12 vfs objects = glusterfs glusterfs:volume = dis-rep12 glusterfs:logfile = /var/log/samba/glusterfs-dis-rep12.log glusterfs:loglevel = 7 path = / read only = no guest ok = yes
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. http://rhn.redhat.com/errata/RHBA-2013-1769.html