|
Paschalis (PeterA in #gluster) has reported these bugs and we've
tried to find the source of the problem to no avail. Worse yet,
there's no way to just reset the quotas to match what's actually
there, as far as I can tell. What should we look for to isolate the source of this problem since this is a production system with enough activity to make isolating the repro difficult at best, and debug logs have enough noise to make isolation nearly impossible? Finally, isn't there some simple way to trigger quota to rescan a path to reset trusted.glusterfs.quota.size ? His production system has been unmanageable for months now. It is possible for someone spare some cycles to get this looked at? 2013-03-04 - https://bugzilla.redhat.com/show_bug.cgi?id=917901 2013-10-24 - https://bugzilla.redhat.com/show_bug.cgi?id=1023134 |
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
