Bug 1490493 - Sub-directory mount details are incorrect in /proc/mounts
Summary: Sub-directory mount details are incorrect in /proc/mounts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: 3.12
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1488913
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-11 18:22 UTC by Vijay Bellur
Modified: 2017-10-13 12:46 UTC (History)
1 user (show)

Fixed In Version: glusterfs-glusterfs-3.12.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1488913
Environment:
Last Closed: 2017-10-13 12:46:24 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Vijay Bellur 2017-09-11 18:22:21 UTC
+++ This bug was initially created as a clone of Bug #1488913 +++

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-11 18:23:22 UTC
REVIEW: https://review.gluster.org/18260 (mount/fuse: Include sub-directory in source argument for mount()) posted (#1) for review on release-3.12 by Vijay Bellur (vbellur)

Comment 2 Worker Ant 2017-09-28 20:52:46 UTC
COMMIT: https://review.gluster.org/18260 committed in release-3.12 by jiffin tony Thottan (jthottan) 
------
commit 68944b104952751b5bd551fe1d84a6bb20962484
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: 1490493
    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>
    (cherry picked from commit 84f8fb81d73b87463092eb082a5cc6a4055103f4)

Comment 3 Jiffin 2017-10-13 12:46:24 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-glusterfs-3.12.2, please open a new bug report.

glusterfs-glusterfs-3.12.2 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/gluster-users/2017-October/032684.html
[2] https://www.gluster.org/pipermail/gluster-users/


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