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". Thanks, -eric On Sun, Aug 11, 2013 at 11:07 AM, Vijay Bellur <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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130811/79702321/attachment-0001.html>
