<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>6.5 on Ubuntu 18<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 10/13/2019 10:14 PM, Amar Tumballi
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CA+OzEQs+C5hxGdj+tJxaGKf_7hafnF0QaXgcqoDeY5qkLF0WDA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">Which is the version of GlusterFS you are using?
        <div><br>
        </div>
        <div>There are few methods like 'gfid2path' option to fetch
          details of the file path from a gfid in versions above v6.0</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, Oct 14, 2019 at 8:14
          AM wkmail &lt;<a href="mailto:wkmail@bneit.com"
            moz-do-not-send="true">wkmail@bneit.com</a>&gt; 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">We
          recently were trying to track down a high load situation on a
          KVM <br>
          node in a cluster running gluster (replication2 + arb).<br>
          <br>
          Iotop on the affected node showed that gluster was involved
          showing <br>
          abnormally heavy writes. There wasn't any obvious activity on
          the <br>
          network coming into the VMs, so it was something internal to
          one of <br>
          them, so we had to keep looking<br>
          <br>
          We then used gluster volume top which showed that a couple of
          shards <br>
          were being pounded but we didn't see a way to immediately
          associate <br>
          those shards with their VM file.<br>
          <br>
          We eventually figured out the problem VM using other methods
          and <br>
          resolved the issue, but we would still like to know if there
          is a script <br>
          or recipe to determine what file a shard may belong to as that
          would <br>
          have sped up the resolution.<br>
          <br>
          -wk<br>
          <br>
          <br>
          <br>
          <br>
          ________<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/118564314"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://bluejeans.com/118564314</a><br>
          <br>
          NA/EMEA Schedule -<br>
          Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
          Bridge: <a href="https://bluejeans.com/118564314"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://bluejeans.com/118564314</a><br>
          <br>
          Gluster-users mailing list<br>
          <a href="mailto:Gluster-users@gluster.org" target="_blank"
            moz-do-not-send="true">Gluster-users@gluster.org</a><br>
          <a
            href="https://lists.gluster.org/mailman/listinfo/gluster-users"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.gluster.org/mailman/listinfo/gluster-users</a><br>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>