I suspect you are missing the patch needed to make this work. http://git.samba.org/?p=samba.git;a=commit;h=872a7d61ca769c47890244a1005c1bd445a3bab6 ; It was put in, in the 3.6.13 timeframe if I'm reading the git history correctly. The bug manifests when the base of the share has a different amount of "Quota Allowance" than elsewhere in the tree. \\foo\ - 5GB quota \\foo\bar - 2.5GB quota When you run "dir" in \\foo you get the results from the 5GB quota, and the same in \\foo\bar, which is incorrect and highly confusing to users. https://bugzilla.samba.org/show_bug.cgi?id=9646 Despite my discussion of "multi-volume" it should be the same bug. Thanks, -Ira / ira at samba.org ----- Original Message ----- From: "David Gibbons" <david.c.gibbons at gmail.com> To: gluster-users at gluster.org Sent: Wednesday, October 30, 2013 11:04:49 AM Subject: Re: Samba vfs_glusterfs Quota Support? Thanks all for the pointers. What version of Samba are you running? Samba version is 3.6.9: [root at gfs-a-1 /]# smbd -V Version 3.6.9 Gluster version is 3.4.1 git: [root at gfs-a-1 /]# glusterfs --version glusterfs 3.4.1 built on Oct 21 2013 09:22:36 It should be # gluster volume set gfsv0 features.quota-deem-statfs on [root at gfs-a-1 /]# gluster volume set gfsv0 features.quota-deem-statfs on volume set: failed: option : features.quota-deem-statfs does not exist Did you mean features.quota-timeout? I wonder if the quota-deem-statfs is part a more recent version? Cheers, Dave _______________________________________________ Gluster-users mailing list Gluster-users at gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users