[Gluster-users] Issues attaching new bricks to existing volume

[Vijay Bellur]

On 01/10/2014 08:12 PM, Chris Pernicano wrote:
> Hello,
>
> I am working to attach some new bricks to an existing gluster volume and
> getting some odd errors. Our current setup is 3 servers each with a 60GB
> brick in replica 3. I'm attempting to add 3 more servers each with a
> 60GB brick. We are running Ubuntu 12.04 and gluster 3.4.2.
>
> Current volume info:
> root at clipart03.vpc240.customink.com
> <mailto:root at clipart03.vpc240.customink.com> ~# gluster volume info
> Volume Name: gv0
> Type: Replicate
> Volume ID: a2319e92-c53c-491e-a36d-1af7a67bf445
> Status: Started
> Number of Bricks: 1 x 3 = 3
> Transport-type: tcp
> Bricks:
> Brick1: clipart01.vpc240.customink.com:/data/gv0/brick1/clipart_archive
> Brick2: clipart01.vpc248.customink.com:/data/gv0/brick1/clipart_archive
> Brick3: clipart02.vpc240.customink.com:/data/gv0/brick1/clipart_archive
>
>
> Command I'm using to add the new bricks:
>
> root at clipart03.vpc240.customink.com
> <mailto:root at clipart03.vpc240.customink.com> ~# gluster volume add-brick
> gv0 clipart02.vpc248.customink.com:/data/gv0/brick1/clipart_archive
> clipart03.vpc240.customink.com:/data/gv0/brick1/clipart_archive
> clipart03.vpc248.customink.com:/data/gv0/brick1/clipart_archive force
> volume add-brick: failed: /data/gv0/brick1/clipart_archive or a prefix
> of it is already part of a volume
>
> Please let me know if you need more information on our setup.
>

Joe Julian's excellent article on resolving this should be of help:

http://joejulian.name/blog/glusterfs-path-or-a-prefix-of-it-is-already-part-of-a-volume/

-Vijay