Hi Kirby,<br><br>As of now, dht does balancing of storage only during creation of files. Files which are already created are not moved b/w nodes because of less free storage.<br><br>During creation dht tries to balance out the storage b/w its children. it accepts an option min-free-disk which is nothing but the minimum percentage of disk space on a node needed for dht to store the file on that node. If the hashed node does not satisfy this criteria, dht stores the actual file on any node which has minimum percentage of free disk configured and stores the a pointer to this node in the hashed node.<br>
<br>regards,<br><div class="gmail_quote">On Wed, Apr 15, 2009 at 6:27 AM, Kirby Zhou <span dir="ltr"><<a href="mailto:kirbyzhou@sohu-rd.com">kirbyzhou@sohu-rd.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If a file grows bigger and bigger, how can glusterfs move it between bricks?<br>
The original bricks are full of space, but newly added bricks are nearly<br>
empty, How can DHT translator deals that situation?<br>
<br>
Thanks<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users" target="_blank">http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Raghavendra G<br><br>