Product SiteDocumentation Site

11.14. Mount and Repair Fails – Corrupted Log

If the log is corrupted you will see an error like:
# mount <filesystem>
mount: Unknown error 990
# dmesg | tail -20
Filesystem “<filesystem>": xfs_inode_recover: Bad inode magic number . . .
Filesystem "dm-0": XFS internal error xlog_recover_do_inode_trans(1) at line 2352 Caller 0xffffffff88307729
XFS: log mount/recovery failed: error 990 XFS: log mount failed
# xfs_repair <device>
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed. Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair. If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
# /usr/sbin/xfs_logprint –C <filename> <device>
# /usr/sbin/xfs_logprint -t <device>
But in this case, the only option may be to throw the log away:
# xfs_repair -L


Destroying the log throws away valuable metadata, and may cause further corruption. Attempt a mount before using -L, and use this option only as a last resort