<div dir="ltr">Hi,<div><br></div><div>In case if you do not want to do a quota enable/disable(which is a cleaner operation) </div><div>you can try this:</div><div><br></div><div>Just a point to add, to what Sanoj has mentioned in the previous mail,</div><div>if you have identified the lowest level directory in the tree where the accounting</div><div>has messed up, you can set "dirty" xattr flag on the directory. By setting a "dirty" flag</div><div>marker will forcefully recalculate(add the sum of children and account to parent) the </div><div>quota values. You can do this by s<span style="color:rgb(0,0,0);white-space:pre-wrap">etting "dirty" flag on (1) a gluster mount which will </span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">set on all the bricks or (2) you </span><span style="color:rgb(0,0,0);white-space:pre-wrap">can do the same </span><span style="color:rgb(0,0,0);white-space:pre-wrap">on a individual directory where </span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">quota accounting has gone </span><span style="color:rgb(0,0,0);white-space:pre-wrap">bad: </span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap">setfattr -n trusted.glusterfs.quota.dirty -v 1 <directory></span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><div class="gmail_extra"><div><div class="gmail-m_-6568255107574456159gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>--</div><div>Thanks & Regards,</div><div>Manikandan Selvaganesan.</div><div>(@Manikandan Selvaganesh on Web)</div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Feb 14, 2017 at 11:42 AM, Sanoj Unnikrishnan <span dir="ltr"><<a href="mailto:sunnikri@redhat.com" target="_blank">sunnikri@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>Hi <span class="gmail-m_-6568255107574456159m_-2455298411106082555gmail-gD" name="lejeczek">lejeczek,<br><br></span>We have seen this issue before. <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1421933" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1421933</a><br></div>The problem here is that the accounting xattr in the backend becomes FFFFF...<br></div>This happens likely due to an underflow (value goes below 0) on some operation like rm/unlink/truncate/mv. We would be adding defensive checks to prevent this, but that will not solve the accounting issue.<br><br></div><div>This is a race and we do not have a consistent reproducer for it yet. <b>Could you describe the operations that were being done on the volume when u ran into this?</b><br></div><div><br>Due to the way quota works, if xattr of any directory goes wrong they get bubbled up to all its ancestors. So, it would also help if we can identify the lowest directory in the tree where the xattr has gone wrong and then try to find the operations on that particular directory. <br></div><div><b>Could you also share the xattr values on all bricks: find . | xargs getfattr -d -m. -e hex </b><br></div><div><div><div><br></div><div>To recover from this you could do a quota disable and enable.<br><br></div><div>Thanks and Regards,<br></div><div>Sanoj<br></div></div></div></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-users</a><br></blockquote></div><br></div></div></div>