Bug 1488913

Summary:	Sub-directory mount details are incorrect in /proc/mounts
Product:	[Community] GlusterFS	Reporter:	Vijay Bellur <vbellur>
Component:	fuse	Assignee:	Vijay Bellur <vbellur>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.13.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1490493 (view as bug list)		Environment:
Last Closed:	2017-12-08 17:40:26 UTC	Type:	---
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:	1490493

Description Vijay Bellur 2017-09-06 12:58:49 UTC

Sub-directory mount gets listed as <hostname>:<volname> in /proc/mounts. Instead it should appear as <hostname>:<volname>/<sub-dir>.

Comment 1 Worker Ant 2017-09-06 13:03:06 UTC

REVIEW: https://review.gluster.org/18210 (mount/fuse: Include sub-directory in source argument for mount()) posted (#2) for review on master by Vijay Bellur (vbellur)

Comment 2 Worker Ant 2017-09-07 09:52:21 UTC

COMMIT: https://review.gluster.org/18210 committed in master by Amar Tumballi (amarts) 
------
commit 84f8fb81d73b87463092eb082a5cc6a4055103f4
Author: Vijay Bellur <vbellur>
Date:   Tue Sep 5 23:58:15 2017 -0400

    mount/fuse: Include sub-directory in source argument for mount()
    
    With this, mount of a sub-directory 'foo' gets listed in /proc/mounts as:
    
    <hostname>:<volname>/foo on /mnt/glusterfs type fuse.glusterfs (rw,relatime...)
    
    Signed-off-by: Vijay Bellur <vbellur>
    BUG: 1488913
    Change-Id: Ib1e1ac3741bf66e1a912d792f2948b748931f2b0
    Reviewed-on: https://review.gluster.org/18210
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: Niels de Vos <ndevos>
    Smoke: Gluster Build System <jenkins.org>
    Reviewed-by: Amar Tumballi <amarts>

Comment 3 Shyamsundar 2017-12-08 17:40:26 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.13.0, please open a new bug report.

glusterfs-3.13.0 has been announced on the Gluster mailinglists [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://lists.gluster.org/pipermail/announce/2017-December/000087.html
[2] https://www.gluster.org/pipermail/gluster-users/