On 06/14/2013 12:55 PM, Jon Tegner wrote:
Maybe my question was a bit "involved", I'll try again:
while searching the web I have found various issues connected to
"cluster.min-free-disk" (e.g., one shouldn't use % but rather a size
number). Would it be possible with an update of the status?
With 3.3.1, the percentage was being interpreted as a number. A
workaround was to configure using bytes and the references allude to this.
Can you explain a bit more about the issue being seen with 3.3.2qa3? Are
new files being created in bricks that are more than 80% full after
setting min.free-disk to 20%?
Regards,
Vijay
Thanks,
/jon
On Jun 11, 2013 16:47 "Jon Tegner" <[email protected]>
<mailto:[email protected]> wrote:
Hi,
have a system consisting of four bricks, using 3.3.2qa3. I used the
command
gluster volume set glusterKumiko cluster.min-free-disk 20%
Two of the bricks where empty, and two were full to just under 80% when
building the volume.
Now, when syncing data (from a primary system), and using min-free-disk
20% I thought new data would go to the two empty bricks, but gluster
does not seem to honor the 20% limit.
Have I missed something here?
Thanks!
/jon
***************gluster volume info************************
Volume Name: glusterKumiko
Type: Distribute
Volume ID: 8f639d0f-9099-46b4-b597-244d89def5bd
Status: Started
Number of Bricks: 4
Transport-type: tcp,rdma
Bricks:
Brick1: kumiko01:/mnt/raid6
Brick2: kumiko02:/mnt/raid6
Brick3: kumiko03:/mnt/raid6
Brick4: kumiko04:/mnt/raid6
Options Reconfigured:
cluster.min-free-disk: 20%
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
