<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000"><div>Emmanuel,</div><div><br></div><div>We (AFR team) had a discussion about this and came to the conclusion that the code doing tryinodelk()s in metadata self-heal can be safely removed, for which I will be sending a patch.</div><div><br></div><div>With this patch (once it is out), could you run this test a couple of times again and let us know if the inodelk collision logs are still appearing?</div><div><br></div><div>-Krutika</div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Emmanuel Dreyfus" <manu@netbsd.org><br><b>To: </b>"Krutika Dhananjay" <kdhananj@redhat.com><br><b>Cc: </b>"Gluster Devel" <gluster-devel@gluster.org><br><b>Sent: </b>Wednesday, December 3, 2014 3:15:23 PM<br><b>Subject: </b>Re: [Gluster-devel] question on glustershd<br><div><br></div>On Wed, Dec 03, 2014 at 04:02:13AM -0500, Krutika Dhananjay wrote:<br>> What was the test that led to this? <br><div><br></div>In tests/basic/afr/entry-self-heal.t the print_pending_heals test line 258<br>spots the problem. It always report spb_heal spb_me_heal. <br><div><br></div>-- <br>Emmanuel Dreyfus<br>manu@netbsd.org<br></blockquote><div><br></div></div></body></html>