Description of problem: With a distribute volume , if you do any replace-brick operation after the replace-brick start will fail saying brick or a prefix of it is already part of a volume. Version-Release number of selected component (if applicable): 1d02db63ae17788c7ab28ac81dea0675500be845 How reproducible:Always Steps to Reproduce: 1.Create a distribute volume. 2.Start a replace-brick with one of the bricks. 3.The run replace-brick status. Actual results:It is failing Expected results:It shouldn't fail Additional info: Volume Name: doa Type: Distribute Volume ID: c6da8c1c-bc21-4ac5-bf9a-59b7cdb2ba1c Status: Started Number of Bricks: 4 Transport-type: tcp Bricks: Brick1: 192.168.1.57:/root/bricks/doa/d1 Brick2: 192.168.1.57:/root/bricks/doa/d2 Brick3: 192.168.1.57:/root/bricks/doa/d3 Brick4: 192.168.1.57:/root/bricks/doa/d4 gluster --mode=script volume replace-brick doa 192.168.1.57:/root/bricks/doa/d1 192.168.1.57:/root/bricks/doa/d5 status /root/bricks/doa/d5 or a prefix of it is already part of a volume
CHANGE: http://review.gluster.com/3354 (glusterd: replace-brick should create dst brick path only once.) merged in master by Vijay Bellur (vijay)