Description of problem: Consecutive volume start/stop operations when ganesha.enable is on, leads to errors Version-Release number of selected component (if applicable): glusterfs-3.7.1-6.el6rhs.x86_64 nfs-ganesha-2.2.0-3.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a 6X2 volume on the ganesha setup 2. Start the volume and enable ganesha, volume gets exported 3. Stop/start the volume, volume gets unexported and exported 4. Again stop the volume, volume does not get unexported. 5. Now if we start the volume, showmount command hangs and times out Actual results: Showmount command hangs Expected results: Showmount command must work successfully Additional info:
gluster vol stop is expected to unexport the volume and the following start is expected to export the volume. This behaviour works fine for one iteration. The second iteration, the export file is created in a slightly different format. Due to this, the volume can never be unexported after this operation. Even 'ganesha.enable' off will not work after this. I have RCAd the problem and will send in a fix soon.
The upstream patch URL is , http://review.gluster.org/#/c/11477/
Consequitive start/stop now exports/unexports the ganesha volume
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