IJ00498: ALTHOUGH JFS2 FSCK SUCCEEDS THE MOUNT OF FILESYSTEM FAILS

APAR status

• Closed as fixed if next.

Error description

• When trying to mount a filesystem you get the following
  error message:
  
  mount: 0506-324 Cannot mount /dev/sas021lv on /sas021: A
  file, file
      system or message queue is no longer available
  
  when fsck runs however nothing is found wrong.
  
  fsck should run and include the following error:
  "Invalid timestamp detected in aggregate inode"
  Proper error is seen if older 5.3 fsck is run on
  filesystem
  
  The fix for this problem will generate the proper error
  message but
  customer still needs to call into AIX support to see if
  patch can be made for filesystem recovery.
  Otherwise customer will need to restore from backup
  
  Problem is rare and probably caused by someone
  accidentally trying to create
  new filesystem and exiting from the command before too
  much damage is done
  

Local fix

• Running older 5.3 fsck will show problem why mount does
  not work
  but Customer must call into support to see if a patch can
  be made
  to recover fileystem.
  

Problem summary

• When trying to mount a filesystem you get the following
  error message:
  mount: 0506-324 Cannot mount /dev/sas021lv on /sas021: A
  file, file system or message queue is no longer available
  
  when fsck runs however nothing is found wrong.
  fsck should run and include the following error:
  Invalid inostamp detected in inode inum
  

Problem conclusion

Temporary fix

Comments

• This APAR is being closed FIN. This means that a solution to
  this APAR is expected to be delivered from IBM in a release
  (if any) to be available within the next 24 months.
  

APAR Information

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

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

  IJ03928

Fix information

Applicable component levels