<div dir="ltr">Thank you for the clarification. <br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Mo., 4. März 2019 um 20:19 Uhr schrieb FNU Raghavendra Manjunath <<a href="mailto:rabhat@redhat.com">rabhat@redhat.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi David,<div><br></div><div>Doing full heal after deleting the gfid entries (and the bad copy) is fine. It is not dangerous. </div><div><br></div><div>Regards,</div><div>Raghavendra</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 4, 2019 at 9:44 AM David Spisla <<a href="mailto:spisla80@gmail.com" target="_blank">spisla80@gmail.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"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hello Gluster Community,</div><div><br></div><div>I have questions and notes concerning the steps mentioned in</div><div><a href="https://github.com/gluster/glusterfs/issues/491" target="_blank">https://github.com/gluster/glusterfs/issues/491</a></div><div><br></div><div>"
<strong>2. Delete the corrupted files</strong>
":</div><div>In my experience there are two GFID files if a copy gets corrupted. Example:</div><div><i>$ find /gluster/brick1/glusterbrick/.glusterfs -name fc36e347-53c7-4a0a-8150-c070143d3b34<br>/gluster/brick1/glusterbrick/.glusterfs/quarantine/fc36e347-53c7-4a0a-8150-c070143d3b34<br>/gluster/brick1/glusterbrick/.glusterfs/fc/36/fc36e347-53c7-4a0a-8150-c070143d3b34<br></i></div><div><i><br></i></div><div><i></i></div><div>Both GFID files has to be deleted. If a copy is NOT corrupted, there seems to be no GFID file in <br></div><div><i>.glusterfs/quarantine . </i>Even one executes scub ondemand, the file is not there.
The file in
<i>.glusterfs/quarantine</i> occurs if one executes "scrub status".</div><div><br></div><div>
"
<strong>3. Restore the file</strong>
":</div><div>One alternatively trigger self heal manually with</div><div><i>gluster vo heal VOLNAME</i></div><div>But in my experience this is not working. One have to trigger a full heal:</div><div>
<i>gluster vo heal VOLNAME</i> <i>full</i></div><div><i><br></i></div><div>Imagine, one will restore a copy with manual self heal. It is neccesary to set some VOLUME options (stat-prefetch, dht.force-readdirp and performance.force-readdirp disabled) and mount via FUSE with some special parameters to heal the file?</div><div>In my experience I do only a full heal after deleting the bad copy and the GFID files.</div><div>This seems to be working. Or it is dangerous?</div><div><br></div><div>Regards</div><div>David Spisla<br></div><div><i></i></div><div><i></i></div><div><i></i><br></div><div><br></div><div><br></div></div></div></div></div></div>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div>
</blockquote></div>