<div dir="ltr">Shyam,<div><br>Thanks. What would be *extremely* useful is the ability to move data off the brick just through replace brick, where the other identified brick is a member of the current cluster (Isn't that something that would be natural?)</div>
<div><br></div><div>The *real* issue for me is that my disk hosts multiple bricks, each of whose replicas are on other bricks (higher redundancy). You can't "remove" a brick without taking out its replica as well. Wouldn't it be much simpler for Gluster to be able to manage this in the backend through replace-brick?</div>
<div><br></div><div>BTW, I also noticed that Gluster doesn't like it if I went down from X replicas to 1 replicas, and the X replica bricks are not specified in the order as obtained from `gluster volume info`.</div><div>
<br></div><div>Thanks,</div><div>Hari</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 30, 2014 at 8:24 PM, Shyamsundar Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> From: "Hariharan Thantry" <<a href="mailto:thantry@gmail.com">thantry@gmail.com</a>><br>
> To: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a><br>
> Sent: Friday, January 31, 2014 4:23:03 AM<br>
> Subject: [Gluster-users] gluster replacing a brick<br>
<div class="im"><br>
> Hi folks,<br>
> Is there an easy way to shrink the size of a gluster volume by replacing some<br>
> of its constituent disks, and moving the data to other constituent disks?<br>
<br>
</div>Wouldn't remove-brick suffice for what you have in mind?<br>
I would think you need to remove-bricks and rebalance to get the data migrated out of the removed bricks, and then decommission those bricks (commit the remove-brick).<br>
<div class="im"><br>
> I did<br>
> gluster volume replace-brick <volname> <old-brick> <new-brick><br>
> where both <old-brick> and <new-brick> are part of the gluster setup, but it<br>
> wouldn't let me do this complaining that:<br>
> Brick: <new-brick> not available. Brick may be containing or be contained by<br>
> an existing brick.<br>
<br>
</div>So <new-brick> is part of the same gluster volume, and hence the error (even if it was part of another gluster volume the same would happen)<br>
<div class="im"><br>
> Can I remove the new-brick, wipe off the gluster artifacts [the trusted.XXX<br>
> parameters], and then do the replace-brick? Will that cause any data loss?<br>
<br>
</div><new-brick> is part of the gluster volume, so wiping off gluster artefacts would in turn result in data loss, or rather gluster failing to see this brick as a part of the volume etc.<br>
<br>
> Thanks,<br>
> Hari<br>
</blockquote></div><br></div>