<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div style="font-family:Arial;"><br></div>
<div><br></div>
<div><br></div>
<div>On Mon, Jul 17, 2017, at 10:53 PM, Nigel Babu wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div style="font-family:Arial;"><br></div>
<div><div defang_data-gmailquote="yes"><blockquote defang_data-gmailquote="yes" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);padding-left:1ex;"><div><div><div><div>On Mon, Jul 17, 2017, at 02:00 PM, Jeff Darcy wrote:<br></div>
<blockquote type="cite"><div style="font-family:Arial;">On Mon, Jul 17, 2017, at 09:28 AM, Nigel Babu wrote:<br></div>
<blockquote type="cite"><div dir="ltr"><div>It appears that something changed in <a href="https://review.gluster.org/#/c/17771">https://review.gluster.org/#/<wbr>c/17771</a>. The tarball with the logs for that patch was 32G. That doesn't sound right. Is something writing to log excessively after this patch landed?<br></div>
</div>
</blockquote><div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">I don't see anything in the patch itself, or in its immediate predecessors, that would account for this. However, it could be a less direct kind of effect. I'll take a look.<br></div>
</blockquote><div style="font-family:Arial;"><br></div>
</div>
</div>
<div style="font-family:Arial;">Are you sure that's the right patch? I looked at the smoke log, which seems quite ordinary, and the regression log is pretty tiny because tests on release-3.8-fb don't actually do much. On the other hand, I don't see any other patches on my list that seem to be likely culprits either<br></div>
</div>
</blockquote></div>
</div>
</div>
</blockquote><div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;">Since the crashes are in brick daemons, I strongly suspect that the crashes are actually from <a href="https://review.gluster.org/#/c/17750/">https://review.gluster.org/#/c/17750/</a> (which does touch server code) rather than 17771 (which does not). I'll try to reproduce the problem here, and then work on a fix.<br></div>
<div style="font-family:Arial;"><br></div>
<div style="font-family:Arial;"><br></div>
</body>
</html>