<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:43, Pranith Kumar
Karampuri пишет:<br>
</div>
<blockquote
cite="mid:CAOgeEnYQ5HjmeAVHv+CH0Pg4O8Kn4KuPb3LS1-9cQAjmx8Fxzw@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:41 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">
<div bgcolor="#FFFFFF" text="#000000">
<div>13.07.2016 07:46, Pranith Kumar Karampuri пишет:<br>
</div>
<span class="">
<blockquote type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Jul 12, 2016 at
9:27 PM, 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">
<div text="#000000" bgcolor="#FFFFFF"> <br>
<br>
<div>12.07.2016 17:39, Pranith Kumar
Karampuri пишет:<br>
</div>
<span>
<blockquote type="cite">
<div dir="ltr">Wow, what are the steps
to recreate the problem?<br>
</div>
</blockquote>
<br>
</span> just set file length to zero,
always reproducible.</div>
</blockquote>
<div><br>
</div>
<div>Changing things on the brick i.e. not
from gluster volume mount is not something
you want to do. In the worst case(I have
seen this only once in the last 5 years
though) where you do this it can lead to
data loss also. So please be aware of it.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</span> Data replication with gluster is a way to avoid
data loss, right? Or no? If not- why use gluster then?<br>
I though that gluster self-healing will heal or at least
report missed files or files with wrong lenths- i.e.
corruptions visible just by reading brick's directory,<br>
not comparing data as bit rot detection...<br>
If this is not a bug, then gluster is not what I
expected :-(<br>
</div>
</blockquote>
<div><br>
</div>
<div>Yes Data replication with gluster is a way to avoid
data loss. Changing files directly on the brick is similar
to changing internal data structures of a disk filesystem.
Or changing the internal files of a database. Things may
stop working as you expect it to. All the hardwork done by
the stack is nullified if you fiddle with the data on the
brick directly. To put it succinctly you enter into the
area of undefined behavior if you start fiddling with the
data on the brick directly. Unless it is a documented
behaviour I suggest you don't do it.<br>
</div>
<div> </div>
<br>
</div>
</div>
</div>
</blockquote>
Sorry, I'm talking not about direct data manipulation in bricks as
way to use gluster, I'm talking about problems detection and
recovery.<br>
As I already said- if I for some reason ( real case can be only by
accident ) will delete file this will not be detected by self-heal
daemon, and, thus, will lead to lower replication level, i.e. lower
failure tolerance. <br>
<br>
<br>
<br>
</body>
</html>