IJ51332: ASSERT EXP(REGP != __NULL) IN LINE 13760 OF FILE

APAR status

• Closed as program error.

Error description

• Stack logged by logAssertFailed: regP != __null on
  mmfs.log file:
  
  
  <TIMESTAMP>: [X] logAssertFailed: regP != __null
  <TIMESTAMP>: [X] return code 0, reason code 0, log record
                   tag 0
  <TIMESTAMP>: [I] Calling user exit script mmUnmountFs:
                   event unmount, Async command
                   /usr/lpp/mmfs/lib/mmsysmon/
                   sendRasEventToMonitor.
  <TIMESTAMP>: [W] sendRasEventToMonitor: Received
                   filesystem SGPanic for
                   filesystem(s)=<FILESYSTEM>
  <TIMESTAMP>: [I] sendRasEventToMonitor: Successfully sent
                   a file system event to the monitor.
  Event
                   code=999295
  <TIMESTAMP>: [I] sendRasEventToMonitor: Successfully sent
                   a file system event to the monitor.
  Event
                   code=999558
  <TIMESTAMP>: [E] Close connection to <IP> <NODE>
                   <CONNECTION>:[1] (Connection reset by
                   peer). Attempting reconnect.
  <TIMESTAMP>: [E] Close connection to <IP> <NODE>
                   <CONNECTION>:[0] (Connection reset by
                   peer). Attempting reconnect.
  <TIMESTAMP>: mmumount: Unmounting file systems ...
  umount: <FILESYSTEM>: target is busy.
  mmumount: Command failed. Examine previous error messages
     to determine cause.
  <TIMESTAMP>: [X] *** Assert exp(regP != __null) in line
     13760 of file /<PATH>/alloc.C
  

Local fix

Problem summary

• GPFS daemon could assert unexpectedly with EXP(REGP != _NULL) in
  file alloc.C.    This could occur on client nodes where there
  are active block allocation activities.
  

Problem conclusion

• This problem is fixed in 5.1.9.5
  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:
  Prevent unexpected GPFS daemon assert.
  
  Work Around:
  None
  
  Problem trigger:
  Block allocation and deallocation activities on a client node
  
  Symptom:
  Abend/Crash
  
  Platforms affected:
  ALL Operating System environments
  
  Functional Area affected:
  All Scale Users
  
  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 ADV

• Fixed component ID

  5737F35AP

Applicable component levels