Bug 1640003

Summary:	improper checking to avoid identical mounts
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Han Han <hhan>
Component:	fuse	Assignee:	Csaba Henk <csaba>
Status:	CLOSED ERRATA	QA Contact:	Nag Pavan Chilakam <nchilaka>
Severity:	high	Docs Contact:
Priority:	low
Version:	unspecified	CC:	amukherj, nchilaka, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	Rebase
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1640026 (view as bug list)		Environment:
Last Closed:	2019-10-30 12:20:13 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:	1640026, 1696807

Description Han Han 2018-10-17 06:56:42 UTC

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:

Comment 2 Worker Ant 2018-10-17 07:40:31 UTC

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

Comment 3 Amar Tumballi 2018-11-26 08:56:52 UTC

The above said patch is now merged upstream. Next rebase to upstream would have the fix.

Comment 6 Amar Tumballi 2019-06-03 11:36:59 UTC

> Amar, I believe this should be fine

Ack! Looks fine for me.

Comment 11 errata-xmlrpc 2019-10-30 12:20:13 UTC

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.

https://access.redhat.com/errata/RHEA-2019:3249