<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">13.07.2016 08:36, Pranith Kumar
Karampuri пишет:<br>
</div>
<blockquote
cite="mid:CAOgeEnYXy=E99ZUPbvCfzk=52pjZgHk5NzSbSh3GASt3nhq+1g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 13, 2016 at 9:35 AM,
Dmitry Melekhov <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:dm@belkam.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:dm@belkam.com">dm@belkam.com</a></a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">13.07.2016
01:52, Anuradha Talur пишет:<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
----- Original Message -----<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
From: "Dmitry Melekhov" <<a
moz-do-not-send="true" href="mailto:dm@belkam.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:dm@belkam.com">dm@belkam.com</a></a>><br>
To: "Pranith Kumar Karampuri" <<a
moz-do-not-send="true"
href="mailto:pkarampu@redhat.com" target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a></a>><br>
Cc: "gluster-users" <<a moz-do-not-send="true"
href="mailto:gluster-users@gluster.org"
target="_blank">gluster-users@gluster.org</a>><br>
Sent: Tuesday, July 12, 2016 9:27:17 PM<br>
Subject: Re: [Gluster-users] 3.7.13, index healing
broken?<br>
<br>
<br>
<br>
12.07.2016 17:39, Pranith Kumar Karampuri пишет:<br>
<br>
<br>
<br>
Wow, what are the steps to recreate the problem?<br>
<br>
just set file length to zero, always reproducible.<br>
<br>
</blockquote>
If you are setting the file length to 0 on one of the
bricks (looks like<br>
that is the case), it is not a bug.<br>
<br>
Index heal relies on failures seen from the mount
point(s)<br>
to identify the files that need heal. It won't be able
to recognize any file<br>
modification done directly on bricks. Same goes for
heal info command which<br>
is the reason heal info also shows 0 entries.<br>
</blockquote>
<br>
</span>
Well, this makes self-heal useless then- if any file is
accidently corrupted or deleted (yes! if file is deleted
directly from brick this is no recognized by idex heal
too), then it will not be self-healed, because self-heal
uses index heal.<span class=""><br>
</span></blockquote>
<div><br>
</div>
<div>It is better to look into bit-rot feature if you want
to guard against these kinds of problems.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Bit rot detects bit problems, not missing files or their wrong
length, i.e. this is overhead for such simple task.<br>
<br>
Thank you!<br>
<br>
<blockquote
cite="mid:CAOgeEnYXy=E99ZUPbvCfzk=52pjZgHk5NzSbSh3GASt3nhq+1g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Heal full on the other hand will individually compare
certain aspects of all<br>
files/dir to identify files to be healed. This is why
heal full works in this case<br>
but index heal doesn't.<br>
</blockquote>
</span>
OK, thank yo for explanation, but , once again how about
self-healing and data consistency?<br>
And, if I access this deleted or broken file from client
then it will be healed, I guess this is what self-heal
needs to do.<br>
<br>
Thank you!
<div class="HOEnZb">
<div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
On Tue, Jul 12, 2016 at 3:09 PM, Dmitry Melekhov
< <a moz-do-not-send="true"
href="mailto:dm@belkam.com" target="_blank">dm@belkam.com</a>
> wrote:<br>
<br>
<br>
<br>
12.07.2016 13:33, Pranith Kumar Karampuri пишет:<br>
<br>
<br>
<br>
What was "gluster volume heal <volname>
info" showing when you saw this<br>
issue?<br>
<br>
just reproduced :<br>
<br>
<br>
[root@father brick]# >
gstatus-0.64-3.el7.x86_64.rpm<br>
<br>
[root@father brick]# gluster volume heal pool<br>
Launching heal operation to perform index self
heal on volume pool has been<br>
successful<br>
Use heal info commands to check status<br>
[root@father brick]# gluster volume heal pool info<br>
Brick father:/wall/pool/brick<br>
Status: Connected<br>
Number of entries: 0<br>
<br>
Brick son:/wall/pool/brick<br>
Status: Connected<br>
Number of entries: 0<br>
<br>
Brick spirit:/wall/pool/brick<br>
Status: Connected<br>
Number of entries: 0<br>
<br>
[root@father brick]#<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On Mon, Jul 11, 2016 at 3:28 PM, Dmitry Melekhov
< <a moz-do-not-send="true"
href="mailto:dm@belkam.com" target="_blank">dm@belkam.com</a>
> wrote:<br>
<br>
<br>
Hello!<br>
<br>
3.7.13, 3 bricks volume.<br>
<br>
inside one of bricks:<br>
<br>
[root@father brick]# ls -l
gstatus-0.64-3.el7.x86_64.rpm<br>
-rw-r--r-- 2 root root 52268 июл 11 13:00
gstatus-0.64-3.el7.x86_64.rpm<br>
[root@father brick]#<br>
<br>
<br>
[root@father brick]# >
gstatus-0.64-3.el7.x86_64.rpm<br>
[root@father brick]# ls -l
gstatus-0.64-3.el7.x86_64.rpm<br>
-rw-r--r-- 2 root root 0 июл 11 13:54
gstatus-0.64-3.el7.x86_64.rpm<br>
[root@father brick]#<br>
<br>
so now file has 0 length.<br>
<br>
try to heal:<br>
<br>
<br>
<br>
[root@father brick]# gluster volume heal pool<br>
Launching heal operation to perform index self
heal on volume pool has been<br>
successful<br>
Use heal info commands to check status<br>
[root@father brick]# ls -l
gstatus-0.64-3.el7.x86_64.rpm<br>
-rw-r--r-- 2 root root 0 июл 11 13:54
gstatus-0.64-3.el7.x86_64.rpm<br>
[root@father brick]#<br>
<br>
<br>
nothing!<br>
<br>
[root@father brick]# gluster volume heal pool full<br>
Launching heal operation to perform full self heal
on volume pool has been<br>
successful<br>
Use heal info commands to check status<br>
[root@father brick]# ls -l
gstatus-0.64-3.el7.x86_64.rpm<br>
-rw-r--r-- 2 root root 52268 июл 11 13:00
gstatus-0.64-3.el7.x86_64.rpm<br>
[root@father brick]#<br>
<br>
<br>
full heal is OK.<br>
<br>
But, self-heal is doing index heal according to<br>
<br>
<a moz-do-not-send="true"
href="http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Developer-guide/afr-self-heal-daemon/"
rel="noreferrer" target="_blank">http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Developer-guide/afr-self-heal-daemon/</a><br>
<br>
Is this bug?<br>
<br>
<br>
As far as I remember it worked in 3.7.10....<br>
<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org"
target="_blank">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://www.gluster.org/mailman/listinfo/gluster-users"
rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
<br>
<br>
<br>
--<br>
Pranith<br>
<br>
<br>
<br>
<br>
--<br>
Pranith<br>
<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gluster-users@gluster.org"
target="_blank">Gluster-users@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://www.gluster.org/mailman/listinfo/gluster-users"
rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote>
</blockquote>
<br>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Pranith<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>