<p dir="ltr"></p>
<p dir="ltr">Sent from Samsung Galaxy S4<br>
On 7 Jun 2015 20:04, "Nathan Hand (Business)" <<a href="mailto:nathanh@manu.com.au">nathanh@manu.com.au</a>> wrote:<br>
><br>
> I have a simple distributed volume with two bricks.<br>
><br>
> # gluster volume info myvolume<br>
> Volume Name: myvolume<br>
> Type: Distribute<br>
> Volume ID: b0193509-817b-4f77-8f65-4cfeb384bedb<br>
> Status: Started<br>
> Number of Bricks: 2<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: zeus.lan:/mnt/pool-lvol1/brick0<br>
> Brick2: io.lan:/data/glusterfs/myvolume/brick2/anchor<br>
><br>
> I’d like to change Brick1’s path to follow Brick2’s naming convention, i.e. /data/glusterfs/myvolume/brick1/anchor<br>
><br>
> I can easily change Brick1’s mount point, but I don’t know how to tell gluster about the new location.<br>
><br>
> Options I’ve considered:<br>
><br>
> * Editing /var/lib/glusterd/vols by hand, but that could be foolish.<br>
> * Adding brick3, removing brick1, adding brick1, removing brick3.<br>
This looks to be the best option IMO. You could go for replace brick option but that doesnt protect you from data loss. <br>
><br>
> Is there a better way? Preferably one that doesn’t need brick3 because I don’t have a brick that large lying around.<br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></p>