APAR status
Closed as program error.
Error description
While running offline fsck the node asserts with signal 11 when checking log files
Local fix
Patch the SGdesc using tsdbfs and make numlogitems to 0 # tsdbfs <fs> patch desc numlogitems 0
Problem summary
While running offline fsck the node asserts with signal 11 when checking log files
Problem conclusion
Benefits of the solution: The fix will prevent the node from asserting and now offline fsck will properly report and fix the bad log file address. Work around: Patch the SGdesc using tsdbfs and make numlogitems to 0 # tsdbfs <fs> patch desc numlogitems 0 Problem trigger: Running offline fsck while deleting the system pool disk. Symptom: Node assert Platforms affected: ALL Operating System environments Functional Area affected: FSCK Customer Impact: Suggested
Temporary fix
Comments
APAR Information
APAR number
IJ31851
Reported component name
SPEC SCALE STD
Reported component ID
5737F33AP
Reported release
505
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-04-09
Closed date
2021-04-09
Last modified date
2021-04-09
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
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"STXKQY","label":"IBM Spectrum Scale"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"505","Line of Business":{"code":"LOB26","label":"Storage"}}]
Document Information
Modified date:
10 April 2021