Bug 1288186

Hey Neil,

We have fixed quite a lot of issues with quota accounting in 3.6 and 3.7. As we have already mentioned on the other bug(#1288195), we need to look into this issue and the regressions the backporting fix could cause. Accordingly, we will fix and you could expect the fix in one of the next upcoming minor release of 3.5. One other way is we can manually fix the same in the backend. If you want to manual fix it, we will update you on how that can be done. 

Thank you :-)

--
Thanks & Regards,
Manikandan Selvaganesh.

Hey Manikandan,

Thanks for looking into backporting the fix to the 3.5 branch! :) 

Thanks much!
Neil

Hi Neil,

While looking at the issue, we suspect the problem could be with dht/afr translator. If you want the disk usage using the df utility to report by taking quota limits into consideration, run the following command:

    # gluster volume set VOLNAME quota-deem-statfs on

In this case, the total disk space of the directory is taken as the quota hard limit set on the directory of the volume and quota will report accordingly when you issue disk usage.

You could find more about the same on [1]

[1] https://gluster.readthedocs.org/en/latest/Administrator%20Guide/Directory%20Quota/

Could you please enable quota-deem-statfs feature and check the usage!

--
Thanks & regards,
Manikandan Selvaganesh.

Hi Manikandan,

I enabled quotas on the volume again and set the "quota-deem-statfs" to "on". The quota counts are no longer being double counted, instead they're just completely incorrect:

[root@storage-1 ~]# gluster volume quota home list
                  Path                   Hard-limit Soft-limit   Used  Available
--------------------------------------------------------------------------------
/test                                     50.0TB       80%       4.6TB  45.4TB

[root@client-1 ~]$ df -h /home/test
Filesystem                        Size  Used Avail Use% Mounted on
storage-1:home                    50T   24T   27T  47% /home

[root@client-1 ~]$ du -sh /home/test
110G    /home/test


Also, I'm seeing the following messages over and over in the brick logs on the Gluster servers:
[2015-12-27 17:32:36.251053] E [marker-quota.c:1830:mq_fetch_child_size_and_contri] (-->/usr/lib64/glusterfs/3.5.5/xlator/features/changelog.so(changelog_setxattr_cbk+0xe3) [0x7fbc69cbc9a3] (-->/usr/lib64/glusterfs/3.5.5/xlator/features/access-control.so(posix_acl_setxattr_cbk+0xb9) [0x7fbc69aad1e9] (-->/usr/lib64/glusterfs/3.5.5/xlator/performance/io-threads.so(iot_setxattr_cbk+0xb9) [0x7fbc6967cc79]))) 0-: Assertion failed: !"uuid null"
[2015-12-27 17:32:36.251085] E [posix.c:136:posix_lookup] 0-home-posix: null gfid for path /user/relax_source/mixed_H30_T40_W15_EC10_51017-51018_V030/673.op001-s23.grd
[2015-12-27 17:32:36.251115] E [posix.c:153:posix_lookup] 0-home-posix: lstat on (null) failed: Invalid argument
[2015-12-27 17:32:36.251136] W [marker-quota.c:1652:mq_update_inode_contribution] 0-home-marker: failed to get size and contribution of path (/user/relax_source/mixed_H30_T40_W15_EC10_51017-51018_V030/673.op001-s23.grd)(Invalid argument)
[2015-12-27 17:32:36.251184] W [marker-quota.c:1416:mq_release_parent_lock] (-->/usr/lib64/glusterfs/3.5.5/xlator/performance/io-threads.so(iot_lookup_cbk+0xd9) [0x7fbc6967edf9] (-->/usr/lib64/libglusterfs.so.0(default_lookup_cbk+0xd9) [0x34ae829469] (-->/usr/lib64/glusterfs/3.5.5/xlator/features/marker.so(mq_update_inode_contribution+0x447) [0x7fbc6925dd07]))) 0-home-marker: An operation during quota updation of path (/user/relax_source/mixed_H30_T40_W15_EC10_51017-51018_V030/673.op001-s23.grd) failed (Invalid argument)

Neil

Hi Neil,

Sorry, at this moment, back porting the fix is not possible since(as mentioned already) there are lot of changes that has gone in 3.7. We are closing this bug as this is not possible to fix in 3.5. Please consider upgrading and let us know if you face any issues in the latest version.


--
Thanks & regards,
Manikandan Selvaganesh.