[Gluster-devel] quota

[Emmanuel Dreyfus]

Vijay Bellur <vbellur at redhat.com> wrote:

> You would need to set features.soft-timeout and features.hard-timeout
> values to 0 when testing with lower values of directory quota.

It works more like expected this way, but there are still oddities: for
instance once quota is reached, I can still append smal chunk to a file,
and do it a lot of times. 

A few debug printf tell me this is because of write-behind: the writing
process gets success, then glusterfs attemps to write - and fail. This
means we silently discard data, which does not looks nice. Is it the
expected behavior or is it a NetBSD bug?

I assume it is expected but undesirable behavior: couldn't we check for
quota space left, and avoid write behind if we aregoing to hit the
barrier?

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu at netbsd.org