[LU-4129] Successive calls to libcfs_debug_dumplog() can result in large number of log files and errors Created: 21/Oct/13  Updated: 03/Mar/14  Resolved: 03/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.2.0
Fix Version/s: Lustre 2.6.0

Type: Bug Priority: Minor
Reporter: Young Jong Pao Assignee: Cliff White (Inactive)
Resolution: Fixed Votes: 0
Labels: patch
Environment:

lustre/libcfs


Severity: 3
Rank (Obsolete): 11177

 Description   

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:

[2009-08-01 00:45:59][c2-0c1s1n0]LustreError: dumping log to /tmp/lustre-log.1249105560.4266
[2009-08-01 00:45:59][c2-0c1s1n0]LustreError: can't open /tmp/lustre-log.1249105560.4266 file: err -17
[2009-08-01 00:45:59][c2-0c1s1n0]LustreError: dumping log to /tmp/lustre-log.1249105560.4266
[2009-08-01 00:45:59][c2-0c1s1n0]LustreError: can't open /tmp/lustre-log.1249105560.4266 file: err -17

This proposed patch will make debug log file name more unique.



 Comments   
Comment by Young Jong Pao [ 22/Oct/13 ]

The patch for LU-4129 has been submitted:
http://review.whamcloud.com/8043

Comment by Peter Jones [ 25/Oct/13 ]

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?

Comment by Cory Spitz [ 28/Oct/13 ]

Let's keep it open and Cray will work on changes to quell the messages.

Comment by Cliff White (Inactive) [ 02/Dec/13 ]

Is Cray still working this issue, or should we close this ticket?

Comment by Cliff White (Inactive) [ 20/Jan/14 ]

Are there any updates on this from Cray?

Comment by Cory Spitz [ 20/Jan/14 ]

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.

Comment by Cliff White (Inactive) [ 20/Jan/14 ]

No problem, I can continue to monitor and nag you, or you can re-assign to one of your people. Either way is fine.

Comment by Ryan Haasken [ 22/Jan/14 ]

I have uploaded a new patch at http://review.whamcloud.com/#/c/8964/

Comment by Ryan Haasken [ 03/Mar/14 ]

The patch has landed.

Generated at Sat Feb 10 01:39:56 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.