Hello, I accidentally sent this question from an email that isn't subscribed to the gluster-users list.
I resent from my mailing list address, but I don't see any of your answers quoted here.
Thanks for your time, I've adjusted the mail recipients to avoid further issues.
-ben
-ben
On Tue, Jul 31, 2018 at 8:02 PM Ashish Pandey <aspandey@xxxxxxxxxx> wrote:
I think I have replied all the questions you have asked.Let me know if you need any additional information.---AshishFrom: "Benjamin Kingston" <ben@xxxxxxxxxxxxxxx>
To: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Tuesday, July 31, 2018 1:01:29 AM
Subject: Increase redundancy on existing disperse volumeI'm working to convert my 3x3 arbiter replicated volume into a disperse volume, however I have to work with the existing disks, maybe adding another 1 or 2 new disks if necessary. I'm hoping to destroy the bricks on one of the replicated nodes and build it into aI'm opting to host this volume on a set of controllers connected to a common backplane, I don't need help on this config, just on the constraints of the disperse volumes.I have some questions about the disperse functionality1. If I create a 1 redundancy volume in the beginning, after I add more bricks, can I increase redundancy to 2 or 32. If I create the original volume with 6TB bricks, am I really stuck with 6TB bricks even if I add 2 or more 10TB bricks3. Is it required to extend a volume by the same number or bricks it was created with? If the original volume is made with 3 bricks, do I have to always add capacity in 3 brick increments?
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
