[Gluster-users] Add brick to a disperse volume

[Ashish Pandey]

Hi, 

Adding bricks to a disperse volume is very easy and same as replica volume. 
You just need to add bricks in the multiple of the number of bricks which you already have. 

So if you have disperse volume with n+k configuration, you need to add n+k more bricks. 
Example : 
If your disperse volume is 4+2, where 2 is the redundancy count, you need to provide 6 (or multiple of 6) bricks (4+2 = 6) when you want to expand or add bricks on your volume. 

I have following volume - 
[root at apandey apandey]# gluster v info 

Volume Name: vol 
Type: Disperse 
Volume ID: 4826eb6e-187d-4ccc-aa89-445338ec3620 
Status: Started 
Snapshot Count: 0 
Number of Bricks: 1 x (4 + 2) = 6 
Transport-type: tcp 
Bricks: 
Brick1: apandey:/home/apandey/bricks/gluster/vol-1 
Brick2: apandey:/home/apandey/bricks/gluster/vol-2 
Brick3: apandey:/home/apandey/bricks/gluster/vol-3 
Brick4: apandey:/home/apandey/bricks/gluster/vol-4 
Brick5: apandey:/home/apandey/bricks/gluster/vol-5 
Brick6: apandey:/home/apandey/bricks/gluster/vol-6 
Options Reconfigured: 
transport.address-family: inet 
performance.readdir-ahead: on 
nfs.disable: on 
[root at apandey apandey]# 

Now, If I want to add bricks in this volume I have to provide bricks in the multiple of 6. It could be 6, 12,18..... 

[root at apandey apandey]# gluster v add-brick vol apandey:/home/apandey/bricks/gluster/newbrick-1 apandey:/home/apandey/bricks/gluster/newbrick-2 apandey:/home/apandey/bricks/gluster/newbrick-3 apandey:/home/apandey/bricks/gluster/newbrick-4 apandey:/home/apandey/bricks/gluster/newbrick-5 apandey:/home/apandey/bricks/gluster/newbrick-6 force 
volume add-brick: success 
[root at apandey apandey]# gluster v info 

Volume Name: vol 
Type: Distributed-Disperse 
Volume ID: 4826eb6e-187d-4ccc-aa89-445338ec3620 
Status: Started 
Snapshot Count: 0 
Number of Bricks: 2 x (4 + 2) = 12 
Transport-type: tcp 
Bricks: 
Brick1: apandey:/home/apandey/bricks/gluster/vol-1 
Brick2: apandey:/home/apandey/bricks/gluster/vol-2 
Brick3: apandey:/home/apandey/bricks/gluster/vol-3 
Brick4: apandey:/home/apandey/bricks/gluster/vol-4 
Brick5: apandey:/home/apandey/bricks/gluster/vol-5 
Brick6: apandey:/home/apandey/bricks/gluster/vol-6 
Brick7: apandey:/home/apandey/bricks/gluster/newbrick-1 
Brick8: apandey:/home/apandey/bricks/gluster/newbrick-2 
Brick9: apandey:/home/apandey/bricks/gluster/newbrick-3 
Brick10: apandey:/home/apandey/bricks/gluster/newbrick-4 
Brick11: apandey:/home/apandey/bricks/gluster/newbrick-5 
Brick12: apandey:/home/apandey/bricks/gluster/newbrick-6 
Options Reconfigured: 
transport.address-family: inet 
performance.readdir-ahead: on 
nfs.disable: on 
[root at apandey apandey]# 

-- 
Ashish 




----- Original Message -----

From: "Michel Lombart" <michellombart at outlook.be> 
To: gluster-users at gluster.org 
Sent: Saturday, August 19, 2017 11:50:31 PM 
Subject: [Gluster-users] Add brick to a disperse volume 



Hello, 



I’m using Gluster since 2 years but only with distributed volumes. 



I’m trying now to set dispersed volumes to have some redundancy. 



I had any problem to create a functional test volume with 4 bricks and 1 redundancy ( Number of Bricks: 1 x (3 + 1) = 4 ). 



I had also any problem to replace a supposed faulty brick with another one. 



My problem is that I can not add a brick to increase the size of the volume as I do with distributed ones. I would have a volume of 5 bricks ( Number of Bricks: 1 x (4 + 1) = 5 ). 



The command « gluster volume add-brick test-volume 10.0.13.192:/data » return « volume add-brick: failed: Incorrect number of bricks supplied 1 with count 4 ». 



The documentation and Google was helpless. 



How can I do ? 



Thank for your help. 



Michel. 









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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170820/f9981a75/attachment.html>