On Tue, Mar 15, 2011 at 6:59 PM, Burnash, James <jburnash at knight.com> wrote: > Hello. > > According to the GlusterFS documentation, adding bricks allows a "replica N" argument in the command line, as show by this phrase from the manual: > > ? ?Brick Commands > > ? ? ? ?volume add-brick VOLNAME [(replica COUNT)|(stripe COUNT)] NEW-BRICK ... > > ? ? ? ? ? ?Add the specified brick to the specified volume. > > I currently have two servers, volume configured like this: > > Volume Name: test-pfs-ro1 > Type: Distributed-Replicate > Status: Started > Number of Bricks: 2 x 2 = 4 > Transport-type: tcp > Bricks: > Brick1: jc1letgfs5:/export/read-only/g01 > Brick2: jc1letgfs6:/export/read-only/g01 > Brick3: jc1letgfs5:/export/read-only/g02 > Brick4: jc1letgfs6:/export/read-only/g02 > Options Reconfigured: > performance.stat-prefetch: on > performance.cache-size: 2GB > network.ping-timeout: 10 > > I want to add the next two servers, which are identically configured with hardware, storage, filesystems, etc. However, adding the bricks using the "replica" argument to indicate that I want this added as another set of mirrors, fails - as seen below: > > gluster volume add-brick test-pfs-ro1 replica 2 jc1letgfs7:/export/read-only/g01 jc1letgfs8:/export/read-only/g01 jc1letgfs7:/export/read-only/g02 jc1letgfs8:/export/read-only/g02 > > wrong brick type: replica, use <HOSTNAME>:<export-dir-abs-path> > Usage: volume add-brick <VOLNAME> <NEW-BRICK> ... > Adding brick to Volume test-pfs-ro1 failed > You needn't specify replica there for add-brick. So it should be, gluster volume add-brick test-pfs-ro1 jc1letgfs7:/export/read-only/g01 jc1letgfs8:/export/read-only/g01 jc1letgfs7:/export/read-only/g02 jc1letgfs8:/export/read-only/g02 - Anush
