Bug 765128 (GLUSTER-3396)

Summary:	object-storage:the mount point names should have the "volume_name"
Product:	[Community] GlusterFS	Reporter:	Saurabh <saurabh>
Component:	object-storage	Assignee:	Gaurav <ggangalw>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Saurabh 2011-08-11 10:56:31 UTC

presently, the mount-point gets created with the AUTH as prefix,

but this may be confusing for the user as he finds the mount points with similar names with AUTH as prefix,

eg, as of now,

for both "auth" and "test" volumes the mount-points created are,
AUTH_a0d83bf31949951cc76352095fa29501  AUTH_bf3919e8b964272200b88376cd231e47

so as per my view this should change and for volumes other than "auth" it should use the volumes name as prefix.

Comment 1 Gaurav 2011-08-12 02:04:36 UTC

Users are not supposed to be aware of mount path. Its used internally by the servers. So its better to be in encoded form. 

One can easily check mounted volume on respective path using mount command.

Comment 2 Saurabh 2011-08-16 03:36:19 UTC

Here, by user I meant the administrator of the cluster.

I understand that the mount command can be used to collect the name for mount-path and volume conjunction and it's trivial, but for the convenience of the administrator we should try to give append/prepend volume name to the mount-path, as it may help shift tasks easily when we are providing integration of object as UFO.