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
REVIEW: http://review.gluster.org/14664 (Prevent creation of volume with name 'gluster_shared_storage') posted (#1) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/14664 (Prevent creation of volume with name 'gluster_shared_storage') posted (#2) for review on master by Samikshan Bairagya (samikshan)
REVIEW: http://review.gluster.org/14664 (Prevent creation of volume with name 'gluster_shared_storage') posted (#3) for review on master by Samikshan Bairagya (samikshan)
This bug is getting closed because GlusteFS-3.7 has reached its end-of-life. Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS. If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.