Bug 824302 - Replace-brick operation tries to create brick directory on all the nodes of a cluster
Summary: Replace-brick operation tries to create brick directory on all the nodes of a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: pre-release
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact: Raghavendra Bhat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-23 08:39 UTC by shylesh
Modified: 2015-11-03 23:04 UTC (History)
3 users (show)

Fixed In Version: glusterfs-3.4.0
Clone Of:
Environment:
Last Closed: 2013-07-24 17:29:18 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions: release-3.3 head: 27bc10d67b9502c03668ca851e8330485cb5e2b5
Embargoed:


Attachments (Terms of Use)

Description shylesh 2012-05-23 08:39:46 UTC
Description of problem:
Replace-brick operation tries to create destination brick directory on all the nodes of the cluster

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

How reproducible:


Steps to Reproduce:
1. create a distribute volume with 2 bricks
say the path of the brick is /path1-to/brick/brick1 /path2-to/brick/brick2

2. fill up with some data and replace the second brick with new brick which has different prefix in the brick path say /path3-to/brick/brick3
3. replace-brick fails
  
Actual results:
It tries to create directories on all the nodes of the cluster , if prefix directories won't exist then it fails saying "could not create the directory"

Expected results:


Additional info:

Comment 1 krishnan parthasarathi 2012-06-19 06:32:22 UTC
http://review.gluster.com/3457 fixes this issue.

Comment 2 Raghavendra Bhat 2012-06-19 12:17:09 UTC
Checked with latest git head [27bc10d67b9502c03668ca851e8330485cb5e2b5] and replace brick is working fine eventhough the destination brick path is not present in other remaining peers of the cluster.


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