<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Still no change in the heals pending. I found this reference,
<a class="moz-txt-link-freetext" href="https://archive.fosdem.org/2017/schedule/event/glusterselinux/attachments/slides/1876/export/events/attachments/glusterselinux/slides/1876/fosdem.pdf">https://archive.fosdem.org/2017/schedule/event/glusterselinux/attachments/slides/1876/export/events/attachments/glusterselinux/slides/1876/fosdem.pdf</a>,
which mentions the default SELinux context for a brick and that
internal operations such as self-heal, rebalance should be
ignored. but they do not elaborate on what ignore means - is it
just not doing self-heal or something else.</p>
<p>I did set SELinux to permissive and nothing changed. I'll try
setting the bricks to the context mentioned in this pdf and see
what happens.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/20/18 8:26 PM, John Strunk wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMLs-gRPSPvjEAvZNZLyNYvruEGvs-v2WL6m=un5v00pXXcMnw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Assuming your bricks are up... yes, the heal count
should be decreasing.
<div><br>
</div>
<div>There is/was a bug wherein self-heal would stop healing but
would still be running. I don't know whether your version is
affected, but the remedy is to just restart the self-heal
daemon.</div>
<div>Force start one of the volumes that has heals pending. The
bricks are already running, but it will cause shd to restart
and, assuming this is the problem, healing should begin...</div>
<div><br>
</div>
<div>$ gluster vol start my-pending-heal-vol force</div>
<div><br>
</div>
<div>Others could better comment on the status of the bug.</div>
<div><br>
</div>
<div>-John</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Thu, Dec 20, 2018 at 5:45 PM Brett Holcomb
<<a href="mailto:biholcomb@l1049h.com"
moz-do-not-send="true">biholcomb@l1049h.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">I
have one volume that has 85 pending entries in healing and two
more <br>
volumes with 58,854 entries in healing pending. These numbers
are from <br>
the volume heal info summary command. They have stayed
constant for two <br>
days now. I've read the gluster docs and many more. The
Gluster docs <br>
just give some commands and non gluster docs basically repeat
that. <br>
Given that it appears no self-healing is going on for my
volume I am <br>
confused as to why.<br>
<br>
1. If a self-heal deamon is listed on a host (all of mine
show one with <br>
a volume status command) can I assume it's enabled and
running?<br>
<br>
2. I assume the volume that has all the self-heals pending
has some <br>
serious issues even though I can access the files and
directories on <br>
it. If self-heal is running shouldn't the numbers be
decreasing?<br>
<br>
It appears to me self-heal is not working properly so how to I
get it to <br>
start working or should I delete the volume and start over?<br>
<br>
I'm running gluster 5.2 on Centos 7 latest and updated.<br>
<br>
Thank you.<br>
<br>
<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></blockquote>
</div>
</blockquote>
</body>
</html>