Bug 763766 (GLUSTER-2034) - Why not start a volume after it has been created?
Summary: Why not start a volume after it has been created?
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2034
Product: GlusterFS
Classification: Community
Component: core
Version: 3.1.0
Hardware: All
OS: Windows
low
low
Target Milestone: ---
Assignee: Vijay Bellur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-28 17:30 UTC by Jacob Shucart
Modified: 2015-12-01 16:45 UTC (History)
4 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jacob Shucart 2010-10-28 17:30:19 UTC 
Can we automatically start a volume once it has been created?  I can't think of a reason why we would not automatically do this.  I have had a couple of customers think that things were broken because they created a volume, went to mount it, and nothing happened.  After looking, it said that the volume was Created, but not started.
Comment 1 Anand Avati 2010-11-25 05:33:58 UTC 
PATCH: http://patches.gluster.com/patch/5780 in master (cli: Enhance message shown upon successful volume creation)
Comment 2 Vijay Bellur 2010-12-02 03:05:06 UTC 
A message has been added to remind the user that a volume needs to be started before accessing data.
Comment 3 Saurabh 2011-03-01 06:27:56 UTC 
[root@centos-qa-2 ~]# /root/glusterfs/inst/sbin/gluster volume create dist2 transport tcp 10.1.12.107:/mnt/bug-dist 10.1.12.107:/mnt/bug-dist1
Creation of volume dist2 has been successful. Please start the volume to access data.
Comment 4 Divya 2011-04-13 06:34:07 UTC 
Added a Note in Creating New Volumes section to start the volume to access data.
Note You need to log in before you can comment on or make changes to this bug.