<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 12, 2021 at 2:14 AM Jeff Byers <<a href="mailto:jbyers.sfly@gmail.com">jbyers.sfly@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Does anyone have any ideas how to prevent, or perhaps<br>
fix the issue described here:<br>
<br>
  Completely filling up a Disperse volume results in<br>
unreadable/unhealable files that must be deleted.<br>
  <a href="https://github.com/gluster/glusterfs/issues/2021" rel="noreferrer" target="_blank">https://github.com/gluster/glusterfs/issues/2021</a><br>
<br>
Cleaning up from this was so terrible when it happened the<br>
first time, that the thought of it happening again is causing<br>
me to lose sleep. :-(<br>
<br>
This was a while ago, but from what I recall from my lab<br>
testing, reserving space with the GlusterFS option, and using<br>
the GlusterFS quota feature only helped some, and didn't<br>
prevent the problem from happening.<br>
<br></blockquote><div><br></div><div class="gmail_default" style="font-size:small">You could perhaps try to reserve some space on the bricks with the  `<span style="color:rgb(32,33,36);font-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap">storage.reserve` option so that you are alerted earlier.  As far as I understand, in disperse volumes, for a file to be healed successfully, all the xattrs and stat information (file size, permissions, uid, gid etc) must be identical on majority of the bricks. If that isn't the case, heal logic cannot proceed further. For </span><i>file.7 </i>in the github issue, I see that <i>trusted.glusterfs.mdata</i> and the file size (from the `ls -l` output) is different on all 3 bricks, so heals won't happen even if there is free space.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">CC'in Xavi to correct me if I am wrong. I'm also not sure if it is possible to partially recover the data from the append writes which were successful before the ENOSPC was hit.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Regards,</div><div class="gmail_default" style="font-size:small">Ravi</div><div class="gmail_default" style="font-size:small"><span style="color:rgb(32,33,36);font-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap"><br></span></div><div class="gmail_default" style="font-size:small"><span style="color:rgb(32,33,36);font-family:Roboto,sans-serif;font-size:14px;white-space:pre-wrap"><br></span></div><div class="gmail_default" style="font-size:small"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thanks!<br>
<br>
~ Jeff Byers ~<br>
________<br>
<br>
<br>
<br>
Community Meeting Calendar:<br>
<br>
Schedule -<br>
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC<br>
Bridge: <a href="https://meet.google.com/cpu-eiue-hvk" rel="noreferrer" target="_blank">https://meet.google.com/cpu-eiue-hvk</a><br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
</blockquote></div></div>