Bug 1026227
| Summary: | quota: volume stop leaves the volume mount with "Transport endpoint is not connected" | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> | |
| Component: | quota | Assignee: | Susant Kumar Palai <spalai> | |
| Status: | CLOSED ERRATA | QA Contact: | Saurabh <saujain> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 2.1 | CC: | agunn, dblack, mzywusko, nsathyan, psriniva, rhs-bugs, spalai, ssamanta, storage-qa-internal, vagarwal, vbellur | |
| Target Milestone: | --- | |||
| Target Release: | RHGS 3.0.0 | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.6.0.5-1.el6rhs | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, stopping a volume would display the message - "Transport end point not connected state" in the quota auxiliary mount. With this fix, quota auxiliary mount is unmounted after the volume stop command is executed.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1049323 (view as bug list) | Environment: | ||
| Last Closed: | 2014-09-22 19:29:22 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: | ||||
| Bug Blocks: | 1049323 | |||
|
Description
Saurabh
2013-11-04 08:57:59 UTC
The problem I am facing with this issue is that, once the volume is stopped and deleted. The mount-point is still there.
If I create a new volume with the same name, now being the information of that same name is still there, hence the gluster volume quota $volname fails,
as can be seen with the example.
[root@quota7 ~]# gluster volume quota dist-rep list
quota: Could not start quota auxiliary mount
[root@quota7 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_quota7-lv_root
42G 6.3G 33G 17% /
tmpfs 4.0G 0 4.0G 0% /dev/shm
/dev/vda1 485M 52M 408M 12% /boot
df: `/var/run/gluster/dist-rep': Transport endpoint is not connected
df: `/var/run/gluster/dist-rep1': Transport endpoint is not connected
/dev/mapper/RHS_vgvdb-RHS_lv1
1.5T 36M 1.5T 1% /rhs/brick1
/dev/mapper/RHS_vgvdc-RHS_lv2
1.6T 35M 1.6T 1% /rhs/brick2
Here the volume in consideration are dist-rep and dist-rep1
and the command "gluster volume quota dist-rep list" failed because of earlier mount info is still there.
Now, it works only if I manually do a "umount".
This is not ok from user experience point of view.
*** Bug 1034880 has been marked as a duplicate of this bug. *** Upstream Fix : http://review.gluster.org/6656 Marking for denali as it got merged as a part of the rebase Fixed in version : glusterfs-3.6.0.5-1.el6rhs [root@nfs1 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_nfs1-lv_root
50G 1.9G 45G 4% /
tmpfs 4.0G 0 4.0G 0% /dev/shm
/dev/vda1 485M 34M 426M 8% /boot
/dev/mapper/vg_nfs1-rhs
425G 3.1G 422G 1% /bricks
localhost:dist-rep 2.5T 16G 2.5T 1% /var/run/gluster/dist-rep
[root@nfs1 ~]# gluster volume stop dist-rep
Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y
volume stop: dist-rep: success
[root@nfs1 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_nfs1-lv_root
50G 1.9G 45G 4% /
tmpfs 4.0G 0 4.0G 0% /dev/shm
/dev/vda1 485M 34M 426M 8% /boot
/dev/mapper/vg_nfs1-rhs
425G 3.1G 422G 1% /bricks
Hence, moving the BZ to verified
Hi Susant, Please review the edited doc text for technical accuracy and sign off. Doc looks good to me. 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/RHEA-2014-1278.html |