Bug 1049323

Summary: quota: volume stop leaves the volume mount with "Transport endpoint is not connected"
Product: [Community] GlusterFS Reporter: Susant Kumar Palai <spalai>
Component: quotaAssignee: Susant Kumar Palai <spalai>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: pre-releaseCC: agunn, bugs, dblack, gluster-bugs, saujain, spalai, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.6.0beta1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1026227 Environment:
Last Closed: 2014-11-11 08:26:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1026227    
Bug Blocks:    

Comment 1 Anand Avati 2014-01-07 12:38:36 UTC
REVIEW: http://review.gluster.org/6656 (quota: unmount quota aux mount for volume stop) posted (#1) for review on master by susant palai (spalai)

Comment 2 Anand Avati 2014-01-07 12:45:09 UTC
REVIEW: http://review.gluster.org/6656 (quota: unmount quota aux mount for volume stop) posted (#2) for review on master by susant palai (spalai)

Comment 3 Anand Avati 2014-01-08 05:30:16 UTC
REVIEW: http://review.gluster.org/6656 (quota: unmount quota aux mount for volume stop) posted (#3) for review on master by susant palai (spalai)

Comment 4 Anand Avati 2014-01-20 12:23:27 UTC
COMMIT: http://review.gluster.org/6656 committed in master by Vijay Bellur (vbellur) 
------
commit b2ef4e3d11af79a765406672bb6ca070b40c9b64
Author: Susant Palai <spalai>
Date:   Mon Jan 6 12:38:08 2014 +0000

    quota: unmount quota aux mount for volume stop
    
    Previously df -h used to display "Transport end point not connected"
    for quota auxiliary mount after volume is stopped. This patch
    unmounts the auxiliary mount when the volume is stopped in all peer
    nodes for that volume.
    
    Change-Id: I78abb44386cd8242a532f92c13df8bdb57c78e31
    BUG: 1049323
    Signed-off-by: Susant Palai <spalai>
    Reviewed-on: http://review.gluster.org/6656
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 5 Niels de Vos 2014-09-22 12:34:41 UTC
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 6 Niels de Vos 2014-11-11 08:26:37 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users