Bug 763207 (GLUSTER-1475) - glusterd should delete brick related files upon remove brick
Summary: glusterd should delete brick related files upon remove brick
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1475
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.1-alpha
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-30 06:42 UTC by Pranith Kumar K
Modified: 2010-08-30 12:54 UTC (History)
1 user (show)

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

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

Description Pranith Kumar K 2010-08-30 06:42:45 UTC 
upon remove-brick command, the brick file and the brick volfile have to be removed. At the moment if we do
volume remove-brick vol <brick>
and do "volume start vol"
Glusterfs process is created for the previous brick that was removed.
Comment 1 Vijay Bellur 2010-08-30 06:52:21 UTC 
PATCH: http://patches.gluster.com/patch/4369 in master (mgmt/glusterd: remove volfile, brick file upon remove-brick)
Note You need to log in before you can comment on or make changes to this bug.