IJ45804: ONLINE MMFSCKX CAN CAUSE NODES TO ASSERT WHEN RUN ON A FILE SYSTEM HAVING MORE THAN 2^32 INODES

APAR status

• Closed as program error.

Error description

• While online mmfsckx is in progress and if a user tries to do
  I/O on a file or directory that has an inode number greater than
   32 bit integer number then in some cases it can cause the node
  to assert with LOGASSERT(i64 == INVALID_INODE_NUMBER || (i64 &
  0xFFFFFFFF00000000ULL) == 0)
  

Local fix

Problem summary

• While online mmfsckx is in progress and if a user tries to do
  I/O on a file or directory that has an inode number greater than
   32 bit integer number then in some cases it can cause the node
  to assert with LOGASSERT(i64 == INVALID_INODE_NUMBER || (i64 &
  0xFFFFFFFF00000000ULL) == 0)
  

Problem conclusion

• This problem is fixed in 5.1.7.1
  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:
  This will prevent the assert when running online mmfsckx.
  
  Work Around:
  None
  
  Problem trigger:
  This issue can only happen when online mmfsckx is run on a file
  system having more than 2^32 inodes (roughly > 4.3billion) and a
  user is doing I/O on a file or directory that has an inode
  number greater than 32 bit while mmfsckx is running.
  
  Symptom:
  Will see the assert LOGASSERT(i64 == INVALID_INODE_NUMBER ||
  (i64 & 0xFFFFFFFF00000000ULL) == 0)
  
  Platforms affected:
  ALL Operating System environments
  
  Functional Area affected:
  FSCKX
  
  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