Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1237053 - Consecutive volume start/stop operations when ganesha.enable is on, leads to errors
Consecutive volume start/stop operations when ganesha.enable is on, leads to ...
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: nfs-ganesha (Show other bugs)
3.1
All Linux
high Severity urgent
: ---
: RHGS 3.1.0
Assigned To: Meghana
Apeksha
:
Depends On: 1238054 1238752
Blocks: 1202842
  Show dependency treegraph
 
Reported: 2015-06-30 05:43 EDT by Apeksha
Modified: 2015-08-31 22:54 EDT (History)
9 users (show)

See Also:
Fixed In Version: glusterfs-3.7.1-7.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1238054 (view as bug list)
Environment:
Last Closed: 2015-07-29 01:08:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1495 normal SHIPPED_LIVE Important: Red Hat Gluster Storage 3.1 update 2015-07-29 04:26:26 EDT

  None (edit)
Description Apeksha 2015-06-30 05:43:36 EDT
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:
Comment 2 Meghana 2015-07-01 01:35:09 EDT
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.
Comment 3 Meghana 2015-07-01 02:48:37 EDT
The upstream patch URL is ,
http://review.gluster.org/#/c/11477/
Comment 6 Apeksha 2015-07-08 06:46:34 EDT
Consequitive start/stop now exports/unexports the ganesha volume
Comment 7 errata-xmlrpc 2015-07-29 01:08:32 EDT
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

Note You need to log in before you can comment on or make changes to this bug.