https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-4129 Lustre <p>Successive calls to libcfs_debug_dumplog() can occur with no delay between calls and can generate a very large number of log files and error messages like this over and over:</p> <p><span class="error">&#91;2009-08-01 00:45:59&#93;</span><span class="error">&#91;c2-0c1s1n0&#93;</span>LustreError: dumping log to /tmp/lustre-log.1249105560.4266<br/> <span class="error">&#91;2009-08-01 00:45:59&#93;</span><span class="error">&#91;c2-0c1s1n0&#93;</span>LustreError: can't open /tmp/lustre-log.1249105560.4266 file: err -17<br/> <span class="error">&#91;2009-08-01 00:45:59&#93;</span><span class="error">&#91;c2-0c1s1n0&#93;</span>LustreError: dumping log to /tmp/lustre-log.1249105560.4266<br/> <span class="error">&#91;2009-08-01 00:45:59&#93;</span><span class="error">&#91;c2-0c1s1n0&#93;</span>LustreError: can't open /tmp/lustre-log.1249105560.4266 file: err -17</p> <p>This proposed patch will make debug log file name more unique.</p> lustre/libcfs LU-4129

Successive calls to libcfs_debug_dumplog() can result in large number of log files and errors

Bug Minor Resolved Fixed Cliff White Young Jong Pao patch Mon, 21 Oct 2013 18:00:44 +0000 Mon, 3 Mar 2014 15:07:33 +0000 Mon, 3 Mar 2014 15:07:33 +0000 Lustre 2.2.0 Lustre 2.6.0 0 5 <p>The patch for <a href="https://jira.whamcloud.com/browse/LU-4129" title="Successive calls to libcfs_debug_dumplog() can result in large number of log files and errors" class="issue-link" data-issue-key="LU-4129"><del>LU-4129</del></a> has been submitted:<br/> <a href="http://review.whamcloud.com/8043" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/8043</a></p> <p>I see that this patch has been abandoned. Shall I close out this ticket or will you reuse it to submit the patch to quieten the error messages?</p> <p>Let's keep it open and Cray will work on changes to quell the messages.</p> <p>Is Cray still working this issue, or should we close this ticket? </p> <p>Are there any updates on this from Cray?</p> <p>Sorry, Cliff. We put this work on hold due to the fact that it was just a minor annoyance and we had bigger fish to fry. Let's keep this open because we still plan to follow up. I just can't say when we'll get back around to it. Ok? If you'd rather re-assign it to someone at Cray we could do that.</p> <p>No problem, I can continue to monitor and nag you, or you can re-assign to one of your people. Either way is fine. </p> <p>I have uploaded a new patch at <a href="http://review.whamcloud.com/#/c/8964/" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/#/c/8964/</a></p> <p>The patch has landed.</p> Development Rank 1|hzw6hj: Rank (Obsolete) 11177 Severity