<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=gb18030">
  </head>
  <body>
    <p>It's my pleasure, CC devel to confirm this issue.<br>
    </p>
    <div class="moz-cite-prefix">在 2019/12/3 14:13, PSC 写道:<br>
    </div>
    <blockquote type="cite"
      cite="mid:tencent_3CF8700F07DD287FD2BCCFFC14904908FD0A@qq.com">
      <meta http-equiv="content-type" content="text/html;
        charset=gb18030">
      <br>
      <div>
        <div>Thank you for your help!</div>
        <div>It seems that it is my fault, I didn't disable quota and
          enable it again, so it seems work fine on commits before
          2fb445ba, when you write file to a volume which had already
          reached its usage limit, it tells Disk quota exceeded. But
          actually, on former commits(before 2fb445ba), if I disable
          quota and enable it again, the volume is crash. You are right!
          2fb445ba addressed the quota issue!<br>
        </div>
        <div><br>
        </div>
        <div>Thank you very much!!<br>
        </div>
        <div><br>
        </div>
        <div style="font-size: 12px;font-family: Arial
          Narrow;padding:2px 0 2px 0;">------------------ 原始邮件 ------------------</div>
        <div style="font-size: 12px;background:#efefef;padding:8px;">
          <div><b>发件人:</b> "zgrep"<a class="moz-txt-link-rfc2396E" href="mailto:zgrep@139.com">&lt;zgrep@139.com&gt;</a>;</div>
          <div><b>发送时间:</b> 2019年11月29日(星期五) 晚上6:35</div>
          <div><b>收件人:</b> "Yaniv Kaul"<a class="moz-txt-link-rfc2396E" href="mailto:ykaul@redhat.com">&lt;ykaul@redhat.com&gt;</a>;<wbr></div>
          <div><b>抄送:</b> "PSC"<a class="moz-txt-link-rfc2396E" href="mailto:1173701037@qq.com">&lt;1173701037@qq.com&gt;</a>;"Gluster
            Devel"<a class="moz-txt-link-rfc2396E" href="mailto:gluster-devel@gluster.org">&lt;gluster-devel@gluster.org&gt;</a>;<wbr></div>
          <div><b>主题:</b> Re: [Gluster-devel] Glusterfs crash when
            enable quota on Arm aarch 64platform.</div>
        </div>
        <div><br>
        </div>
        <p>NO, this issue disappered since commit 2fb445ba.   <br>
        </p>
        <div class="moz-cite-prefix">在 2019/11/29 18:12, Yaniv Kaul 写道:<br>
        </div>
        <blockquote type="cite"
cite="mid:CAJgorsYZZkZ=Qt-TJVJnZGYfnz8id2Fb_KdFjah0UFY8ia-1TQ@mail.gmail.com">
          <div dir="auto">Does it happen on master? </div>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Fri, 29 Nov 2019, 12:06
              Xie Changlong &lt;<a href="mailto:zgrep@139.com"
                moz-do-not-send="true">zgrep@139.com</a>&gt; wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div>
                <p>Hi, PSC<br>
                </p>
                <p>We encounter the same issue a few month ago, and git
                  bisect says the first bad commit is 2fb445ba. This
                  patch is not quota related, but it addressed the quota
                  issue! <br>
                </p>
                <p>Maybe it's gcc issue?? <br>
                </p>
                <p>commit 2fb445babdd621b71676e40804fe98e95fc9084d<br>
                  Author: Xavi Hernandez <a
                    href="mailto:xhernandez@redhat.com" target="_blank"
                    rel="noreferrer" moz-do-not-send="true">&lt;xhernandez@redhat.com&gt;</a><br>
                  Date:   Thu Jan 31 08:13:58 2019 +0100<br>
                  <br>
                      syncop: remove unnecessary call to
                  gf_backtrace_save()<br>
                  <br>
                      A call to gf_backtrace_save() was done on each
                  context switch of a<br>
                      synctask. The backtrace is generated writing to
                  the filesystem, so it<br>
                      can have an important impact on latency.<br>
                  <br>
                      The generated backtrace was not used anywhere, so
                  it's been removed.<br>
                  <br>
                      Change-Id:
                  I399a93b932c5b6e981c696c72c3e1ef44710ba52<br>
                      Updates: bz#1193929<br>
                      Signed-off-by: Xavi Hernandez <a
                    href="mailto:xhernandez@redhat.com" target="_blank"
                    rel="noreferrer" moz-do-not-send="true">&lt;xhernandez@redhat.com&gt;</a><br>
                  <br>
                  diff --git a/libglusterfs/src/glusterfs/syncop.h
                  b/libglusterfs/src/glusterfs/syncop.h<br>
                  index 7a6167b..e0f1017 100644<br>
                  --- a/libglusterfs/src/glusterfs/syncop.h<br>
                  +++ b/libglusterfs/src/glusterfs/syncop.h<br>
                  @@ -73,7 +73,6 @@ struct synctask {<br>
                       int done;<br>
                  <br>
                       struct list_head waitq; /* can wait only "once"
                  at a time */<br>
                  -    char btbuf[GF_BACKTRACE_LEN];<br>
                   };<br>
                  <br>
                   struct syncproc {<br>
                  diff --git a/libglusterfs/src/syncop.c
                  b/libglusterfs/src/syncop.c<br>
                  index bf70daf..6206d4c 100644<br>
                  --- a/libglusterfs/src/syncop.c<br>
                  +++ b/libglusterfs/src/syncop.c<br>
                  @@ -327,7 +327,6 @@ synctask_yield(struct synctask
                  *task)<br>
                  <br>
                       if (task-&gt;state != SYNCTASK_DONE) {<br>
                           task-&gt;state = SYNCTASK_SUSPEND;<br>
                  -        (void)gf_backtrace_save(task-&gt;btbuf);<br>
                       }<br>
                       if (swapcontext(&amp;task-&gt;ctx,
                  &amp;task-&gt;proc-&gt;sched) &lt; 0) {<br>
                           gf_msg("syncop", GF_LOG_ERROR, errno,
                  LG_MSG_SWAPCONTEXT_FAILED,<br>
                </p>
                <p><br>
                </p>
                <div>在 2019/11/29 16:12, PSC 写道:<br>
                </div>
                <blockquote type="cite"> Hi, I am studying on port
                  glusterfs to ARM platform. I compiled and ran it. Most
                  of its functions works fine, however, when I enable
                  quota on any kind of volume, and mount it, and try to
                  read or write anything to the volume. It will run into
                  crash, and tell me the "Transport endpoint is not
                  connected".
                  <div><br>
                  </div>
                  <div>The version of glusterfs I am using is GlusterFS
                    3.12.2.</div>
                  <div>And I test it from version 3.12.2 to 6.0. This
                    problem was solved on 6.0, but I didn't found any
                    addressed Bugs relate to quota.</div>
                  <div>I also do some test on x86 servers, quota works
                    fine. </div>
                  <div><br>
                  </div>
                  <div>On both of x86 and ARM servers, I am using CentOS
                    7.6.</div>
                  <div><br>
                  </div>
                  <div>For stability reason, I had been told that I
                    should use GlusterFS 3.12.2, rather than new
                    versions. So I need to find out how to address this
                    bug.</div>
                  <div><br>
                  </div>
                  <div>Please offer me some help. Thank you very much!!</div>
                  <div><br>
                  </div>
                  <br>
                  <fieldset></fieldset>
                  <pre>_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: <a href="https://bluejeans.com/441850968" target="_blank" rel="noreferrer" moz-do-not-send="true">https://bluejeans.com/441850968</a>


NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: <a href="https://bluejeans.com/441850968" target="_blank" rel="noreferrer" moz-do-not-send="true">https://bluejeans.com/441850968</a>

Gluster-devel mailing list
<a href="mailto:Gluster-devel@gluster.org" target="_blank" rel="noreferrer" moz-do-not-send="true">Gluster-devel@gluster.org</a>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" target="_blank" rel="noreferrer" moz-do-not-send="true">https://lists.gluster.org/mailman/listinfo/gluster-devel</a>

</pre>
                </blockquote>
              </div>
              _______________________________________________<br>
              <br>
              Community Meeting Calendar:<br>
              <br>
              APAC Schedule -<br>
              Every 2nd and 4th Tuesday at 11:30 AM IST<br>
              Bridge: <a href="https://bluejeans.com/441850968"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://bluejeans.com/441850968</a><br>
              <br>
              <br>
              NA/EMEA Schedule -<br>
              Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
              Bridge: <a href="https://bluejeans.com/441850968"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://bluejeans.com/441850968</a><br>
              <br>
              Gluster-devel mailing list<br>
              <a href="mailto:Gluster-devel@gluster.org" target="_blank"
                rel="noreferrer" moz-do-not-send="true">Gluster-devel@gluster.org</a><br>
              <a
                href="https://lists.gluster.org/mailman/listinfo/gluster-devel"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
              <br>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>