<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/17/2016 10:40 AM, Krutika
Dhananjay wrote:<br>
</div>
<blockquote
cite="mid:CAPhYV8Mpys2y4w4ewMhMQ6TRYdoQ2SOw6ghMq0QuWAS-Zrmipg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Good question.<br>
<br>
Any attempt from a client to access /.shard or its contents
from the mount point will be met with an EPERM (Operation not
permitted). We do not expose .shard on the mount point.<br>
<br>
</div>
</div>
</blockquote>
<br>
Just to be clear, I was referring to the shard xlator accessing the
participant shard by sending a named lookup when we access the file
(say 'cat /mount/file > /dev/null`) from the mount.<br>
I removed a shard and its hard-link from one of the bricks of a 2
way replica, unmounted the client, stopped and started the volume
and did read the file from a fresh mount. For some reason (I need to
debug why), a reverse heal seems to be happening where both bricks
of the 2-replica volume end up with zero byte file for the shard in
question.<br>
-Ravi<br>
<br>
<blockquote
cite="mid:CAPhYV8Mpys2y4w4ewMhMQ6TRYdoQ2SOw6ghMq0QuWAS-Zrmipg@mail.gmail.com"
type="cite">
<div dir="ltr">-Krutika<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Aug 17, 2016 at 10:04 AM,
Ravishankar N <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On 08/17/2016 07:25 AM, Lindsay Mathieson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
On 17 August 2016 at 11:24, Ravishankar N <<a
moz-do-not-send="true"
href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@redhat.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
The right way to heal the corrupted files as of now is
to access them from<br>
the mount-point like you did after removing the
hard-links. The list of<br>
files that are corrupted can be obtained with the
scrub status command.<br>
</blockquote>
<br>
Hows that work with sharding where you can't see the
shards from the<br>
mount point?<br>
<br>
</blockquote>
</span>
If sharding xlator does a named lookup of the shard in
question as and when it is accessed, AFR can heal it. But
I'm not sure if that is the case though. Let me check and
get back.<br>
-Ravi
<div class="HOEnZb">
<div class="h5"><br>
<br>
<br>
______________________________<wbr>_________________<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<wbr>/listinfo/gluster-users</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>