Bug 796603

Summary:	[FEAT] `gluster volume create' should create parent directories during volume creation
Product:	[Community] GlusterFS	Reporter:	Sachidananda Urs <sac>
Component:	cli	Assignee:	Krutika Dhananjay <kdhananj>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	pre-release	CC:	aavati, amarts, gluster-bugs, kparthas, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-14 06:14:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sachidananda Urs 2012-02-23 10:00:33 UTC

Description of problem:

When `gluster volume create' is executed, parent directories are not created during volume creation.

If a larger number of nodes exist during volume creation it is cumbersome to login to each node to create the necessary parent directories.

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

How reproducible:

Always

Steps to Reproduce:
1. gluster volume create foo node1:/tmp/1/2/non/existant/dir
2.
3.
  
Actual results:
Unable to create volume, directory does not exist.

Expected results:
Should create the necessary parent directories on the fly.

Additional info:

Comment 1 Amar Tumballi 2012-02-23 10:06:06 UTC

Need policy makers to approve this.

Last debate was if by mistake user did '/data/glsuter/exprot/vol1' instead of '/data/gluster/export/vol1', he may end up creating a directory with wrong name.

One thing we can do is we can add a 'force' option to volume create, which can create parent directories.

Comment 2 krishnan parthasarathi 2012-08-24 08:43:05 UTC

Kaushal,
Could you confirm that the following patch fixes this bug?
http://review.gluster.com/3378

Comment 3 Krutika Dhananjay 2013-03-14 06:14:14 UTC

The requested behavior is already implemented in upstream. Hence, closing the bug.