<html><head></head><body style="font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;">Maybe my question was a bit "involved", I'll try again:<div><br></div><div>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?</div><div><br></div><div>Thanks,</div><div><br></div><div>/jon</div><div><br><div><div><br></div><div><br></div><div><br><p>On Jun 11, 2013 16:47 "Jon Tegner" <a href="mailto:tegner@renget.se"><tegner@renget.se></a> wrote:</p><blockquote type="cite">Hi,<br><br><br><br>have a system consisting of four bricks, using 3.3.2qa3. I used the<br>command<br><br><br><br><br>gluster volume set glusterKumiko cluster.min-free-disk 20%<br><br><br><br>Two of the bricks where empty, and two were full to just under 80% when<br>building the volume.<br><br><br><br>Now, when syncing data (from a primary system), and using min-free-disk<br>20% I thought new data would go to the two empty bricks, but gluster<br>does not seem to honor the 20% limit.<br><br><br><br>Have I missed something here?<br><br><br><br>Thanks!<br><br><br><br>/jon<br><br><br><br><br><br><br><br>***************gluster volume info************************<br><br><br><br><br>Volume Name: glusterKumiko<br><br>Type: Distribute<br><br>Volume ID: 8f639d0f-9099-46b4-b597-244d89def5bd<br><br>Status: Started<br><br>Number of Bricks: 4<br><br>Transport-type: tcp,rdma<br><br>Bricks:<br><br>Brick1: kumiko01:/mnt/raid6<br><br>Brick2: kumiko02:/mnt/raid6<br><br>Brick3: kumiko03:/mnt/raid6<br><br>Brick4: kumiko04:/mnt/raid6<br><br>Options Reconfigured:<br><br>cluster.min-free-disk: 20%<br><br><br><br><br><br></blockquote></div></div></div></body></html>