Gluster users - Aug 2011 - cluster.min-free-disk separate for each brick

Hello,

I have a gluster set up with very different brick sizes.

brick1: 9T
brick2: 9T
brick3: 37T

with this configuration if I set the parameter cluster.min-free-disk to 10% it 
applies to all bricks which is quite uncomfortable with these brick sizes, 
because 10% for the small bricks are ~ 1T but for the big brick it is ~3.7T and 
what happens at the end is that if all brick go to 90% usage and I continue 
writing, the small ones eventually fill up to 100% while the big one has enough 
free space.

My question is, is there a way to set cluster.min-free-disk per brick instead 
setting it for the entire volume or any other way to work around this problem ?

Thank you in advance

Regards,
Deyan

>
>
> My question is, is there a way to set cluster.min-free-disk per brick
> instead setting it for the entire volume or any other way to work around
> this problem ?
>
>
As of now, there are only two ways one can use 'min-free-disk'. It is
either
with % (default is 10%), or with size, (in KB/MB/GB/TB). With size option,
you can have a hardbound on min-free-disk which will be constant on all the
bricks regardless of its size. We don't have a per brick min-free-disk
option yet.

Regards,
Amar
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20110817/884ede89/attachment.html>