<div dir="ltr"><div><div><div>Seems that nobody is answering my concern :)<br><br></div>I think these post partially answer my question, but I think I still need to perform the experiment to understand more:<br><br><a href="http://gluster.org/pipermail/gluster-users/2011-February/006649.html">http://gluster.org/pipermail/gluster-users/2011-February/006649.html</a><br>
<a href="http://gluster.org/pipermail/gluster-users/2011-February/006642.html">http://gluster.org/pipermail/gluster-users/2011-February/006642.html</a><br><a href="http://review.gluster.com/#/c/158/">http://review.gluster.com/#/c/158/</a><br>
<a href="http://www.ashishnepal.com/glusterfs-centos/">http://www.ashishnepal.com/glusterfs-centos/</a><br><br></div>Review-158 is the most detail info I found on the Internet, and did not found it in any Gluster documentation.<br>
<br></div>Maybe I should start my own wiki collecting all the information found on the Internet.<br><br>Thanks.<br><div><div><div><br><br><br><div><br></div></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jan 8, 2014 at 10:48 AM, Sharuzzaman Ahmat Raslan <span dir="ltr"><<a href="mailto:sharuzzaman@gmail.com" target="_blank">sharuzzaman@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>Hi all,<br><br></div>I have not tested this yet, but would like to get your comment.<br><br></div>I have a customer that is currently running BackupPC system, and the local disk is steadily going to run out of space soon.<br>
<br></div>So I'm thinking of helping this customer move the storage to gluster<br><br></div>They have limited budget, so buying new machine with big disk is not an option. But, they have a couple of old machine available, and the disk size differs in each of them<br>
<br></div>So, I'm planning to grow the storage slowly for them.<br><br></div>The first step that I think is to get 2 replicated storage nodes, so that redundancy can be increased.<br><br></div>Once that work, I'm planning to introduce another node to get a distributed-replicated system. This is the part that I'm not sure.<br>
<br></div>Let say the customer have nodes like this:<br></div>node1: 100GB (p1n1)<br></div>node2: 200GB (p1n2,p2n2)<br></div>node3: 300GB (p1n3)<br><br></div>node1 is currently the single BackupPC storage. I can partition node2 to get a 100GB (p1n2), then join with node1 (p1n1) to get a replicated gluster storage.<br>
<br></div>When I introduce node3 later, I plan to use the extra 100GB from node2 (p2n2), to join with 100GB from node3 (p1n3). Now, I have 4 bricks defined. 1 brick in node1 (p1n1), 2 brick in node2 (p1n2,p2n2), and 1 brick in node3 (p1n3).<br>
<br></div>The question is, how to change from replicated system (p1n1-p1n2), to distributed-replicated [(p1n1-p1n2)(p2n2-p1n3)] in a running system?<br><br></div>Ideas?<br><br>Thanks.<span class="HOEnZb"><font color="#888888"><br>
<div><div><br><div><div><div><div>
<div><div><div><div><div><div><div><div><div><div><div><br>-- <br>Sharuzzaman Ahmat Raslan
</div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br>Sharuzzaman Ahmat Raslan
</div>