APAR status
Closed as program error.
Error description
The file system fails to mount, and the mmfs.log.latest on the file system manager node has an error related to "Log recovery failed". Often this kind of error results from one or more NSDs being offline, and the solution is to restart those disks. Failing that, this kind of error can still usually be worked around with a mmfsck command, but due to an error in the way this bad log is handled, the mmfsck cannot continue either. The mmfsck command also complains of the log recovery failure. In this state, the file system cannot be mounted, even in read-only mode. Neither can the log be repaired in order for recovery to continue.
Local fix
Problem summary
Disk problem could cause newly created log files to become inconsistent and this in turn could cause file system panic during log recovery. All attempt to mount the file system will fail when this occurs.
Problem conclusion
Better handle inconsistent log file that contain no valid log data and prevent file system will fail when this occurs.
Temporary fix
Comments
APAR Information
APAR number
IJ22788
Reported component name
SPEC SCALE DME
Reported component ID
5737F34AP
Reported release
503
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-02-14
Closed date
2020-02-26
Last modified date
2020-02-26
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 DME
Fixed component ID
5737F34AP
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"503","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
26 February 2020