Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1640026

Summary:	improper checking to avoid identical mounts
Product:	[Community] GlusterFS	Reporter:	Han Han <hhan>
Component:	fuse	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, csaba, rhinduja, rhs-bugs, sankarshan, storage-qa-internal
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1640003	Environment:
Last Closed:	2019-03-25 16:31:24 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:	1640003
Bug Blocks:

Description Han Han 2018-10-17 07:31:59 UTC

+++ This bug was initially created as a clone of Bug #1640003 +++

Description of problem:
As suject.

Version-Release number of selected component (if applicable):
glusterfs-fuse-3.12.2-19.el7rhgs.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Mount a fuse sshfs to /mnt
# sshfs -o allow_other,nonempty root.4.183:/tmp/mkdir /mnt

2. Mount a glusterfs to the same mount points
# mount -t glusterfs 10.66.4.183:/gv0 /mnt/                     
/sbin/mount.glusterfs: according to mtab, GlusterFS is already mounted on /mnt

The error message it not correct. Glusterfs is actually not mounted.


Actual results:
As step2

Expected results:
Glusterfs could mount.

Additional info:

--- Additional comment from Red Hat Bugzilla Rules Engine on 2018-10-17 02:56:47 EDT ---

This bug is automatically being proposed for a Z-stream release of Red Hat Gluster Storage 3 under active development and open for bug fixes, by setting the release flag 'rhgs‑3.4.z' to '?'. 

If this bug should be proposed for a different release, please manually change the proposed release flag.

Comment 1 Worker Ant 2018-10-17 07:40:34 UTC

REVIEW: https://review.gluster.org/21405 (mount.glusterfs: A more explicit check to avoid identical mounts) posted (#5) for review on master by

Comment 2 Worker Ant 2018-10-24 10:19:31 UTC

COMMIT: https://review.gluster.org/21405 committed in master by "Amar Tumballi" <amarts> with a commit message- mount.glusterfs: A more explicit check to avoid identical mounts

Change check condition from
"[[:space:]+]${mount_point}[[:space:]+]fuse" to
"[[:space:]+]${mount_point}[[:space:]+]fuse.glusterfs". Fix false
postive check result for mount points of other FUSEes, such as "fuse.sshfs".

Change-Id: I13898b50a651a8f5ecc3a94d01b3b5de37ec4cbc
fixes: bz#1640026
Signed-off-by: Han Han <hhan>

Comment 3 Shyamsundar 2019-03-25 16:31: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-6.0, please open a new bug report.

glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/