CentOS Stream 10 – Common Problem 184 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Filesystem fails to mount with ‘log mount failed’ or ‘corrupt log’.

Environment & Reproduction

Triggered by power loss or storage path failures.

xfs_info /dev/mapper/vg-data
dmesg | tail

Root Cause Analysis

XFS log replay encountered an inconsistent transaction.

Quick Triage

Capture device metadata before any repair attempt.

xfs_metadump /dev/mapper/vg-data /root/xfs.dump

Step-by-Step Diagnosis

Confirm whether the filesystem is unmounted and try xfs_repair.

umount /data || true
xfs_repair -n /dev/mapper/vg-data

Solution – Primary Fix

Run xfs_repair to clean the log and reconcile metadata.

xfs_repair /dev/mapper/vg-data
mount /data

Solution – Alternative Approaches

If repair fails, zero the log as a last resort after backup.

xfs_repair -L /dev/mapper/vg-data

Verification & Acceptance Criteria

Filesystem mounts and applications start without errors.

mount | grep /data
touch /data/.ok && rm /data/.ok

Rollback Plan

Restore the metadump if repair makes things worse.

xfs_mdrestore /root/xfs.dump /dev/mapper/vg-data

Prevention & Hardening

Use UPS-backed storage and enable barrier=1.

mount -o remount,nobarrier=0 /data

Related Errors & Cross-Refs

Log replay failed, structure needs cleaning warnings.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

xfs_repair man page, kernel xfs notes.