[Gluster-users] can you change a brick's mount point?

Gaurav Garg ggarg at redhat.com
Sun Jun 7 18:23:13 UTC 2015


comments inline.

----- Original Message -----
From: "Atin Mukherjee" <atin.mukherjee83 at gmail.com>
To: "Nathan Hand (Business)" <nathanh at manu.com.au>
Cc: gluster-users at gluster.org
Sent: Sunday, June 7, 2015 8:08:19 PM
Subject: Re: [Gluster-users] can you change a brick's mount point?





Sent from Samsung Galaxy S4 
On 7 Jun 2015 20:04, "Nathan Hand (Business)" < nathanh at manu.com.au > wrote: 
> 
> I have a simple distributed volume with two bricks. 
> 
> # gluster volume info myvolume 
> Volume Name: myvolume 
> Type: Distribute 
> Volume ID: b0193509-817b-4f77-8f65-4cfeb384bedb 
> Status: Started 
> Number of Bricks: 2 
> Transport-type: tcp 
> Bricks: 
> Brick1: zeus.lan:/mnt/pool-lvol1/brick0 
> Brick2: io.lan:/data/glusterfs/myvolume/brick2/anchor 
> 
> I’d like to change Brick1’s path to follow Brick2’s naming convention, i.e. /data/glusterfs/myvolume/brick1/anchor 
> 
> I can easily change Brick1’s mount point, but I don’t know how to tell gluster about the new location. 
> 
> Options I’ve considered: 
> 
>> * Editing /var/lib/glusterd/vols by hand, but that could be foolish. 
> >* Adding brick3, removing brick1, adding brick1, removing brick3. 

By editing /var/lib/glusterd/vols you might miss something to edit. Adding and removing brick option seems good.

>This looks to be the best option IMO. You could go for replace brick option but that doesnt protect you from data loss. 
> 
> Is there a better way? Preferably one that doesn’t need brick3 because I don’t have a brick that large lying around. 
> _______________________________________________ 
> Gluster-users mailing list 
> Gluster-users at gluster.org 
> http://www.gluster.org/mailman/listinfo/gluster-users 

_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users


More information about the Gluster-users mailing list