e above, we can also do,
> setfattr -n trusted.glusterfs.quota.dirty -v 1 /home/export/ptop-1/dir
>
> regards,
> Raghavendra
>
> - Original Message -
>> From: "Manikandan Selvaganesh"
>> To: "Sergei Gerasenko"
>> Cc: "Sergei Gerasen
er-users"
>
> Sent: Tuesday, August 30, 2016 10:57:33 PM
> Subject: Re: [Gluster-users] incorrect usage value on a directory
>
> Hi Sergei,
>
> Apologies for the delay. I am extremely sorry, I was struck on something
> important
> It's great that you figured out the
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
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 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
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,
Sergei
> On Aug 29, 2016, at 3:41 PM, Sergei Gerasenko wro
I found an informative thread on a similar problem:
http://www.spinics.net/lists/gluster-devel/msg18400.html
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
Just to be clear, I’m talking about the usage reported by the gluster vol quota
list command.
> On Aug 11, 2016, at 9:31 AM, Sergei Gerasenko 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 clust
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,
Sergei
> On Aug 9, 2016, at 7:26 AM, Mani
Hi Sergei,
When quota is enabled, quota-deem-statfs should be set to ON(By default
with the recent versions). But apparently
from 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//info.
If you do not find a
Hi ,
The gluster version is 3.7.12. Here’s the output of `gluster info`:
Volume Name: ftp_volume
Type: Distributed-Replicate
Volume ID: SOME_VOLUME_ID
Status: Started
Number of Bricks: 3 x 2 = 6
Transport-type: tcp
Bricks:
Brick1: host03:/data/ftp_gluster_brick
Brick2: host04:/data/ftp_gluster_br
Hi,
Sorry, I missed the mail. May I know which version of gluster you are using
and please paste the output of
gluster v info?
On Sat, Aug 6, 2016 at 8:19 AM, Sergei Gerasenko wrote:
> Hi,
>
> I'm playing with quotas and the quota list command on one of the
> directories claims it uses 3T, wher
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
Glust
12 matches
Mail list logo
