IJ42748: LOGASSERTFAILED: FILEID.INODENUM > 0

APAR status

• Closed as program error.

Error description

• logAssertFailed: fileId.inodeNum > 0 while creation of
  psnap0 which failed due to home cluster filesystem
  unreachable
  

Local fix

• The assert in happening while acquiring a lock on a inode
  and that inode is less than 0 (invalid) and this is
  happening in a function which marks the remote mount as
  unmounted (as it was unresponsive )
  Since this inode number (fileset root inode number) is
  being populated while loading of the fileset pointer it
  cannot be an invalid node. So the fix to have additional
  checks to handle conditions when inode number is invalid.
  

Problem summary

• Assertion: exp(fileId.inodeNum > 0)
  

Problem conclusion

• This problem is fixed in 5.1.2 PTF 8
  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:
  No more assert.
  
  Work around:
  None.
  
  Problem trigger:
  Over stressed Filesystems with AFM DR
  bi-directional relationships running
  
  Symptom:
  Crash
  
  Platforms affected:
  All Linux OS Environments (Acting as AFM Gateway nodes).
  
  Functional Area affected:
  AFM
  
  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