<p dir="ltr"></p>
<p dir="ltr">On 10-Nov-2016 20:52, "Vijay Bellur" <<a href="mailto:vbellur@redhat.com">vbellur@redhat.com</a>> wrote:<br>
><br>
> On Thu, Nov 10, 2016 at 10:16 AM, Manikandan Selvaganesh<br>
> <<a href="mailto:manikandancs333@gmail.com">manikandancs333@gmail.com</a>> wrote:<br>
> > Enabling/disabling quota or removing limits are the ways in which quota.conf<br>
> > is regenerated to the later version. It works properly. And as Pranith said,<br>
> > both enabling/disabling takes a lot of time to crawl(though now much faster<br>
> > with enhanced quota enable/disable process) which we cannot suggest the<br>
> > users with a lot of quota configuration. Resetting the limit using<br>
> > limit-usage does not work properly. I have tested the same. The workaround<br>
> > is based on the user setup here. I mean the steps he exactly used in order<br>
> > matters here. The workaround is not so generic. However, quota<br>
> > enable/disable would regenerate the file on any case.<br>
> ><br>
> > IMO, this bug is critical. I am not sure though how often users would hit<br>
> > this - Updating from 3.6 to latest versions. From 3.7 to latest, its fine,<br>
> > this has nothing to do with this patch.<br>
> ><br>
><br>
> Given that we are done with the last release in 3.6.x, I think there<br>
> would be users looking to upgrade. My vote is to include the<br>
> necessary patches in 3.9 and not let users go through unnatural<br>
> workflows to get quota working again in 3.9.0.</p>
<p dir="ltr">+1, especially considering this is a ".0" release. </p>
<p dir="ltr">><br>
> Thanks,<br>
> Vijay<br>
> _______________________________________________<br>
> maintainers mailing list<br>
> <a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/maintainers">http://www.gluster.org/mailman/listinfo/maintainers</a><br></p>