On 05/23/2014 10:11 PM, Thierry Lamoureux wrote:
Hello, I have a problem using GlusterFS Quota on a distributed volume. Here is my conf : - GlusterFS 3.5 (LATEST) - 3 servers - 1 brick of 10TB per server Once my server have been added to the pool, I've performed the following commands : - gluster volume create vol0 server1:/glusterfs/brick1/vol0 server2:/glusterfs/brick2/vol0 server3:/glusterfs/brick3/vol0 - gluster volume start vol0 - gluster volume set vol0 features.quota-timeout 5
features.quota-timeout can be set to 0 to ensure that quota enforcement happens in a correct manner. However, setting this option can result in reduced client throughput.
- gluster volume quota vol0 enable - gluster volume quota vol0 limit-usage /quota-test 50MB First of all, the last command doesn't work if the "quota-test" folder isn't created, contrary to what it is mentioned in the GlusterFS documentation : "You can set the disk limit on the directory even if it is not created"
Yes, this is expected behavior with the new quota implementation in 3.5. This needs to be corrected in documentation.
-Vijay _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
