Hi Sergei,
--
Apologies for the delay. I am extremely sorry, I was struck on something important
It's great that you figured out the solution.
Whenever you set a dirty flag as mentioned in the previous thread, the quota values will be recalcualted.
Yep, as you mentioned there are lot of changes that has gone in from 3.7. We have
introduced Inode-quota feature in 3.7, then we have implemented the Quota versioning
in 3.7.5 and then enhance quota enable/disable feature in 3.7.12. So a lot of code changes
has been done.
In case would you like to know more, you can refer our specs[1].
On Tue, Aug 30, 2016 at 9:27 PM, Sergei Gerasenko <gerases@xxxxxxxxx> wrote:
The problem must have started because of an upgrade to 3.7.12 from an older version. Not sure exactly how.On Aug 30, 2016, at 10:44 AM, Sergei Gerasenko <gerases@xxxxxxxxx> wrote:It seems that it did the trick. The usage is being recalculated. I’m glad to be posting a solution to the original problem on this thread. It’s so frequent that threads contain only incomplete or partially complete solutions.Thanks,SergeiOn Aug 29, 2016, at 3:41 PM, Sergei Gerasenko <sgerasenko74@xxxxxxxxx> wrote:I found an informative thread on a similar problem:According to the thread, it seems that the solution is to disable the quota, which will clear the relevant xattrs and then re-enable the quota which should force a recalc. I will try this tomorrow.On Thu, Aug 11, 2016 at 9:31 AM, Sergei Gerasenko <gerases@xxxxxxxxx> wrote:Hi Selvaganesh,Thanks so much for your help. I didn’t have that option on probably because I originally had a lower version of cluster and then upgraded. I turned the option on just now.The usage is still off. Should I wait a certain time?Thanks,SergeiOn Aug 9, 2016, at 7:26 AM, Manikandan Selvaganesh <mselvaga@xxxxxxxxxx> wrote:Hi Sergei,When quota is enabled, quota-deem-statfs should be set to ON(By default with the recent versions). But apparentlyfrom your 'gluster v info' output, it is like quota-deem-statfs is not on.Could you please check and confirm the same on /var/lib/glusterd/vols/<VOLNAME>/info. If you do not find an option 'features.quota-deem-statfs=on', then this feature is turned off. Did you turn off this one? You could turn it on by doing this 'gluster volume set <VOLNAME> quota-deem-statfs on'.To know more about this feature, please refer here[1]On Tue, Aug 9, 2016 at 5:43 PM, Sergei Gerasenko <gerases@xxxxxxxxx> wrote:Hi ,The gluster version is 3.7.12. Here’s the output of `gluster info`:Volume Name: ftp_volumeType: Distributed-ReplicateVolume ID: SOME_VOLUME_IDStatus: StartedNumber of Bricks: 3 x 2 = 6Transport-type: tcpBricks:Brick1: host03:/data/ftp_gluster_brickBrick2: host04:/data/ftp_gluster_brickBrick3: host05:/data/ftp_gluster_brickBrick4: host06:/data/ftp_gluster_brickBrick5: host07:/data/ftp_gluster_brickBrick6: host08:/data/ftp_gluster_brickOptions Reconfigured:features.quota: onThanks for the reply!! I thought nobody would reply at this point :)SergeiOn Aug 9, 2016, at 6:03 AM, Manikandan Selvaganesh <mselvaga@xxxxxxxxxx> wrote:Hi,Sorry, I missed the mail. May I know which version of gluster you are using and please paste the output ofgluster v info?On Sat, Aug 6, 2016 at 8:19 AM, Sergei Gerasenko <gerases@xxxxxxxxx> wrote:Hi,I'm playing with quotas and the quota list command on one of the directories claims it uses 3T, whereas the du command says only 512G is used.Anything I can do to force a re-calc, re-crawl, etc?Thanks,Sergei
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users --Regards,Manikandan Selvaganesh.--Regards,Manikandan Selvaganesh.
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
Regards,
Manikandan Selvaganesh._______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
