IO06247: NSR #10325425661 - REISERFS BECOMES CORRUPT - PMR #59724,005,000

APAR status

• Closed as suggestion for future release.

Error description

• We have come across some bad IBM RAID controllers which have
  managed to severely harm the file systems on some of our
  servers.  Essentially the machine will boot up, I presume some
  corruption of the journal occurs, after which every subsequent
  reboot of the machine the file system is read-only.  We
  attempted to correct the file system by doing a Reiserfsck
  -?rebuild-tree, after which the file system seems to be ?okay?.
  Unfortunately, the system will still reboot into read-only
  mode, and it looks as though the repair has left the file
  system in a worse state than it was originally.
  
  They are currently trying to find a better course of action for
  recovery that is is along the line of their system they had in
  place beforehand(RedHat6.2 using EXT2) were an fsck would
  recover their systems most of the time.
  
  I checked the Namesys website and googled a bit but did not find
  anything specific on reiserfs recovery other than a commercial
  product.
  

Local fix

• Rebuild system.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• PROBLEM: After converting to IRES and ReiserFS and incurring a
  RAID controller failure customer reports that recovery is not
  as easy as with RH 6.2 and EXT2.  Are there better tools to use
  for filesystem recovery other than reiserfsck?
  
  
  RESOLUTION: No, there is not tool which can do more as the
  orginal reiserfsck.
  

APAR Information

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

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

Fix information

Applicable component levels