Description of problem: Once a volume is stopped and started again, it is suppose to be in list of exports of nfs-ganesha server and this is exactly not the case right now. Version-Release number of selected component (if applicable): glusterfs-3.7.0-2.el6rhs.x86_64 nfs-ganesha-2.2.0-0.el6.x86_64 How reproducible: always Steps to Reproduce: 1. create volume of type 6x2, start it 2. bring up nfs-ganesha, after completing all pre-requisites 3. showmount -e localhost 3. stop the volume and start the volume again 4. showmount -e localhost Actual results: intially, the vol3 was shown in export list, as can be found here [root@nfs1 ~]# showmount -e localhost Export list for localhost: /vol2 (everyone) /vol3 (everyone) then I tried to stop and start the volume in sequence, [root@nfs1 ~]# gluster volume stop vol3 Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y volume stop: vol3: success so, once the volume is stopped it should not be part of the export list and the result is also similar [root@nfs1 ~]# showmount -e localhost Export list for localhost: /vol2 (everyone) now start the volume, [root@nfs1 ~]# gluster volume start vol3 volume start: vol3: success so now the volume is still not in export list [root@nfs1 ~]# showmount -e localhost Export list for localhost: /vol2 (everyone) Expected results: The volume should be in export list once the volume is started Additional info:
Issue still persisit. After stop and then start of volume, the volume does not get exported.
Volume do gets exported after volume start followed by volume stop
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://rhn.redhat.com/errata/RHSA-2015-1495.html