Bug 829673 - VDSM: No handling for creating a brick in a directory that doesn't exist
Summary: VDSM: No handling for creating a brick in a directory that doesn't exist
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Shireesh
QA Contact: Sudhir D
URL:
Whiteboard: gluster, storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-07 09:12 UTC by Daniel Paikov
Modified: 2013-07-03 06:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-15 08:12:06 UTC
Embargoed:


Attachments (Terms of Use)
engine.log (54.96 KB, application/x-compressed-tar)
2012-06-07 09:12 UTC, Daniel Paikov
no flags Details
vdsm.log (624.98 KB, application/x-compressed-tar)
2012-06-07 09:13 UTC, Daniel Paikov
no flags Details

Description Daniel Paikov 2012-06-07 09:12:23 UTC
Created attachment 590139 [details]
engine.log

When trying to create a brick in a sub-directory of a directory that doesn't exist, the brick creation fails. For example, try to create a brick in /dir1/dir2 while /dir1 doesn't exist.

Comment 1 Daniel Paikov 2012-06-07 09:13:03 UTC
Created attachment 590140 [details]
vdsm.log

Comment 3 Shireesh 2012-06-07 12:20:37 UTC
This is the behavior of GlusterFS, and user is expected to create appropriate brick directories before issuing the command. GlusterFS creates only the leaf level directories if required.

This will be documented in the current release. In the long term, we plan to provide a GUI where user selects disks / partitions in which the bricks are to be created, and in that case, the system will take care of creating appropriate directories before invoking the gluster command.

Comment 4 Shireesh 2012-06-15 08:12:06 UTC
Since there is no response to above comment for quite some time, I assume that the explanation is acceptable.


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