<html><body><div style="font-family: garamond,new york,times,serif; font-size: 12pt; color: #000000"><div><br></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>"Emmanuel Dreyfus" <manu@netbsd.org>, "Gluster Devel" <gluster-devel@gluster.org><br><b>Sent: </b>Friday, December 5, 2014 4:42:59 PM<br><b>Subject: </b>Re: [Gluster-devel] question on glustershd<br><div><br></div>On Fri, Dec 05, 2014 at 04:28:49AM -0500, Krutika Dhananjay wrote:<br>> Here's the patch I was talking about: http://review.gluster.org/#/c/9240/1 <br><div><br></div>Unfortunately it does not fix entry-self-heal.t which still fails at the<br>same place. I wonder if the same change should not be done also on inode<br>lock attempts that are done in data and entry heal code.<br></blockquote><div><br></div><div>Could you provide the trace logs you had added with this failure?</div><div>-Krutika</div><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;">OTOH, it seems to have fixed self-heald.t which suffered a similar problem<br>on the test commented as "Test that ongoing IO is not considered as <br>Pending heal"<br><div><br></div>I have to test a bit more to be sure.<br><div><br></div>-- <br>Emmanuel Dreyfus<br>manu@netbsd.org<br></blockquote><div><br></div></div></body></html>