IJ40754: RUNNING A BLOCKING TRACE WHEN THE NODE IS LOW ON MEMORY AND SWAPPING, CAN LEAD TO A DEADLOCK.

APAR status

• Closed as program error.

Error description

• Running a blocking trace when the node is low
  on memory and swapping, can lead to a deadlock.
  

Local fix

• Ensure that sufficient free memory is available,
  so that the trace tool is not being swapped out.
  

Problem summary

• Running a blocking trace when the node is low
  on memory and swapping, can lead to a deadlock.
  

Problem conclusion

• This problem is fixed in 5.1.2 PTF 6
  To see all Spectrum Scale APARs and
  their respective fix solutions refer to page
  https://public.dhe.ibm.com/storage/spectrumscale/spectrum_scale_
  apars.html
  
  Benefits of the solution:
  Running traces in blocking mode is now
  more reliable in low-memory situations.
  
  Work around:
  Ensure that sufficient free memory is available,
  so that the trace tool is not being swapped out.
  Problem trigger:
  Run traces in blocking mode, while the available memory
  is low and processes are getting swapped out.
  Symptom:  Hang/Deadlock/Unresponsiveness/Long Waiters
  Platforms affected: ALL Linux OS environments
  Functional Area affected: Trace
  Customer Impact: High Importance
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels