Bug 765128 (GLUSTER-3396) - object-storage:the mount point names should have the "volume_name"
Summary: object-storage:the mount point names should have the "volume_name"
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-3396
Product: GlusterFS
Classification: Community
Component: object-storage
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Gaurav
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-11 10:56 UTC by Saurabh
Modified: 2011-08-16 06:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

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.


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