Bug 796603 - [FEAT] `gluster volume create' should create parent directories during volume creation
Summary: [FEAT] `gluster volume create' should create parent directories during volume...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: pre-release
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Krutika Dhananjay
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-23 10:00 UTC by Sachidananda Urs
Modified: 2013-03-14 06:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-14 06:14:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


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