Gluster users - Aug 2015 - Quota going crazy

Hi,

I'm experiencing strange quota mismatch (too much/too few) with 3.6.4 on a
setup which is already an upgrade from the 3.4 series.

In an attempt to reset quota and check from scratch without breaking service I
disabled quota and reset quota-related xattrs on every file on every brick (this
is a 3?2 setup on 6 bricks of 40TB each).
I then re-enabled the quotas, waited a bit for the quota daemons to wakeup and
then I launched a `find` on one of the quota-limited subdirectories. It computed
the right size.
But on another (bigger) directory, the size was a little too small. I re-started
the same `find`, and the final size was much much greater than the real size
(provided by `du`). It should be around 4.1TB and it showed something like 5.4!
I relaunched the same `find` again and again but it continued to grow, until
around 12.6 TB. Next I ran the `find` on another client and? again a growth.

I'm running out of idea right now. If any of you had an idea about what I
could do? thanks in advance.

--
Jonathan Michalon

Hi Jonathan,

Are there any error related to quota in the brick log?

Thanks,
Vijay


On Friday 28 August 2015 12:22 PM, Jonathan MICHALON
wrote:
> Hi,
>
> I'm experiencing strange quota mismatch (too much/too few) with 3.6.4
on a setup which is already an upgrade from the 3.4 series.
>
> In an attempt to reset quota and check from scratch without breaking
service I disabled quota and reset quota-related xattrs on every file on every
brick (this is a 3?2 setup on 6 bricks of 40TB each).
> I then re-enabled the quotas, waited a bit for the quota daemons to wakeup
and then I launched a `find` on one of the quota-limited subdirectories. It
computed the right size.
> But on another (bigger) directory, the size was a little too small. I
re-started the same `find`, and the final size was much much greater than the
real size (provided by `du`). It should be around 4.1TB and it showed something
like 5.4!
> I relaunched the same `find` again and again but it continued to grow,
until around 12.6 TB. Next I ran the `find` on another client and? again a
growth.
>
> I'm running out of idea right now. If any of you had an idea about what
I could do? thanks in advance.
>
> --
> Jonathan Michalon
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users