Bug 829673

Summary: VDSM: No handling for creating a brick in a directory that doesn't exist
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Daniel Paikov <dpaikov>
Component: rhscAssignee: Shireesh <shireesh>
Status: CLOSED WONTFIX QA Contact: Sudhir D <sdharane>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: hateya, shtripat, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: gluster, storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-15 08:12:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log
none
vdsm.log none

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.