On 08/11/13 03:41, Eric Rosel wrote: > Thanks for the reply. > Already been to that page, it only describes how to create volumes. > It does not explain how to interpret the output of "gluster volume info". > They are interpreted in the same manner. (implicitly) on a replica 2 volume... Brick1 + Brick2 = replica set Brick3 + Brick4 = replica set Brick5 + Brick6 = replica set ... on a replica 3 volume... Brick1 + Brick2 + Brick3 = replica set Brick4 + Brick5 + Brick6 = replica set Brick7 + Brick8 + Brick9 = replica set ... > On Sun, Aug 11, 2013 at 11:07 AM, Vijay Bellur <vbellur at redhat.com > <mailto:vbellur at redhat.com>> wrote: > > On 08/11/2013 06:30 AM, Eric Rosel wrote: > > Hi All, > > I have this volume on a test cluster: > > =====<snip>===== > [root at node01 ~]# gluster volume info > Volume Name: backups > Type: Distributed-Replicate > Volume ID: 26fe7c5f-c15b-4054-b7ef-__bf6bfae828df > Status: Started > Number of Bricks: 2 x 2 = 4 > Transport-type: tcp > Bricks: > Brick1: 192.168.2.1:/export/brick1 > Brick2: 192.168.2.2:/export/brick1 > Brick3: 192.168.2.1:/export/brick2 > Brick4: 192.168.2.2:/export/brick2 > =====<snip>===== > > How does one determine which bricks are "replicas" and which > bricks are > used for "distribute"? There are only 2 nodes here, would all > the data > in the volume still be accessible if one node were to go down? > > Apologies if this has been discussed or documented before, > please just > point me to the appropriate link. > > > This might help: > > https://github.com/gluster/__glusterfs/blob/master/doc/__admin-guide/en-US/markdown/__admin_setting_volumes.md#__creating-distributed-__replicated-volumes > <https://github.com/gluster/glusterfs/blob/master/doc/admin-guide/en-US/markdown/admin_setting_volumes.md#creating-distributed-replicated-volumes> > > -Vijay > > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users > -- Mr. Flibble King of the Potato People
