[Gluster-users] Problem with free space limits on servers.

[Basavanagowda Kanur]

option alu.limits.min-free-disk  20%

specifies to unify that stop scheduling new files (create, symlink, mknod)
to a subvolume once the free disk space on the subvolume reaches upto 80% of
total disk space. scheduler does not guarantee that the already created
files won't grow in size.

in fact, min-free-disk option stops scheduling to the subvolumes to allow
the already existing files to grow.

--
gowda


On Wed, Dec 17, 2008 at 2:27 PM, Lior Goikhburg <glior at hh.ru> wrote:

> Got unify over AFR with scheduler ALU. (gluster 1.4 rc1).
>
> volume files-afr1
>  type cluster/afr
>  subvolumes client1 client2
> end-volume
>
> volume files-afr2
>  type cluster/afr
>  subvolumes client3 client4
> end-volume
>
> volume ns-afr
>  type cluster/afr
>  subvolumes ns1 ns2
> end-volume
>
> volume files-unify
>  type cluster/unify
>  option namespace ns-afr
>  subvolumes files-afr1 files-afr2
>  option self-heal background
>  option scheduler alu
>  option alu.limits.min-free-disk  20%
>
> Did a test to completely fill up the space on mounted drive, to see what
> happens.
> All nodes got filled up to 100% despite the limit of 20% on nodes.
> Why is this happening ?
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
>



-- 
hard work often pays off after time, but laziness always pays off now
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20081217/16f642bc/attachment.html>