Hi Jochen, The reason why you see such kind of distribution is:
1. You started off with a single brick volume, and hence the complete hash is the single brick. 2. You added 2 brick, and issued rebalance. Now during rewriting of layout (rebalancing), layout's are calculated to reduce the amount data migrated. So, overlaps are considered. In your scenario, 1st brick always got the start range, and others the remaining in a round robin. With regards, Shishir _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
