Description of problem: The child directory created within parent directory ( on which the quota is set ) shows the entire volume size, when checked with "df" command. Version-Release number of selected component (if applicable):glusterfs-3.4.0.44rhs-1.el6rhs.x86_64 How reproducible:Always Steps to Reproduce: 1.Configure 2x2 volume 2.Enable quota and set deem-statfs to on 3.Set Limit usage to 200MB and soft limit to 80 or 90% on say /test directory 4.Mount the volume on a client, Create subdirectory under /test and run df command to the subdirectory Actual results: # gluster volume quota test_data list Path Hard-limit Soft-limit Used Available -------------------------------------------------------------------------------- /test 200.0MB 90% 0Bytes 200.0MB <----------------quota set on /test 200MB # df -h /quota_test/test/ Filesystem Size Used Avail Use% Mounted on 10.65.211.178:/test_data 200M 0 200M 0% /quota_test <---------------correct info for /test , 200MB [root@dhcp210-101 /]# df -h /quota_test/test/test123 Filesystem Size Used Avail Use% Mounted on 10.65.211.178:/test_data 896M 33M 863M 4% /quota_test <-------------------- Incorrect information for a child directory inside /test/test123 , it is showing 863M , that is the size of entire volume. Expected results: df -h /quota_test/test/ Filesystem Size Used Avail Use% Mounted on 10.65.211.178:/test_data 200M 0 200M 0% /quota_test # df -h /quota_test/test/test123 Filesystem Size Used Avail Use% Mounted on 10.65.211.178:/test_data 200M 0 200M 0% /quota_test Additional info: In the commit message of the quota patch. (Commit ID on upstream master ab3ab1978a4768e9eed8e23b47e72b25046e607a) "If limit is set on the directory passed, use size/limits on that directory to populate statvfs. Otherwise, use size/limits configured on root." But customer needs this logic to be changed, where anything under the directory where quota is set also returns quota limit via statvfs.
verified on glusterfs-3.6.0.15-1.el6rhs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-1278.html