[Bugs] [Bug 1321978] New: [RFE] Prevent creation of volume with volume name 'gluster_shared_storage'

bugzilla at redhat.com bugzilla at redhat.com
Tue Mar 29 13:48:22 UTC 2016


https://bugzilla.redhat.com/show_bug.cgi?id=1321978

            Bug ID: 1321978
           Summary: [RFE] Prevent creation of volume with volume name
                    'gluster_shared_storage'
           Product: GlusterFS
           Version: 3.7.9
         Component: glusterd
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: sasundar at redhat.com
                CC: bugs at gluster.org



Description of problem:
------------------------
The internal shared storage for gluster was named as -
'gluster_shared_storage'.
This shared storage is created by enabling enable_shared_storage option.

This volume shouldn't get created by hand

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
gluster 3.7.9

How reproducible:
-----------------
N/A

Actual results:
---------------
One can create a volume with the volume name as - 'gluster_shared_storage'

Expected results:
------------------
Creation of volume with volume name - 'gluster_shared_storage' should be
prevented

Additional info:
----------------
1. creation of volume name by name 'all' is prevented, as 'all' will be used by
gluster to refer to all the volumes. None can create a volume by name 'all'

Consequence now is that, I created a volume by name 'gluster_shared_storage'
and while stopping such a volume, gluster thinks that it is the gluster
internal volume and throws warning, which is incorrect

[root@ ~ ]# gluster volume create gluster_shared_storage host1:/brick/brick1
[root@ ~ ]# gluster volume start gluster_shared_storage
[root@ ~ ]# gluster volume stop gluster_shared_storage
Stopping the shared storage volume(gluster_shared_storage), will affect
features like snapshot scheduler, geo-replication and NFS-Ganesha. Do you still
want to continue? (y/n) n

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list