狀況1：app
[sda] Assuming drive cache: write throughide
Internal error xfs XFS_WANT_CORRUPTED_GOTO at line 1662 of file fs/xfs/libxfs/xfs_alloc.c Caller xfs_free_extent+0x130 [xfs]post
Internal error xfs_trans_cancel at line 990 of file fs/xfs/xfs_trans.c.Caller xlog_recover_process_efi +0x16b/0x190 [xfs]fetch
Corruption of in-memory data detected. Shutting down filesystemthis
Please umount the filesystem and rectify the problem(s)spa
Failed to recover EFIscode
Generating "/run/initramfs/rdsosreport.txt"htm
若是是LVM管理分區的blog
ls -l /dev/mapper
xfs_repair /dev/mapper/cl_muban-root
若提示
xfs_repair -L /dev/mapper/cl_muban-root
最後重啓
init 6
狀況2：
[sda] Assuming drive cache: write through
Metadata corruption detected at xfs_agi_read_verify+0x5e/0x110 [xfs], xfs_agi block 0x2
Unmount and run xfs_repair
First 64 bytes of corrupted metadata buffer:
XFS (dm-0)：metadata I/O error: block 0x2 ("xfs_trans_read_buf_map") error 117 numblks 1
修復步驟：
ls -l /dev/mapper
mkdir /mnt
mount /dev/mapper/cl_muban-root /mnt # 這裏也能夠操做 提示中的 dm-0 (即 /dev/dm-0，其實/dev/mapper/cl_muban-root是連接到 /dev/dm-0 )
umount /mnt
xfs_repair /dev/mapper/cl_muban-root # 或 xfs_repair /dev/dm-0
init 6 (reboot重啓系統)
xfs_repair使用方法：
xfs_repair -h xfs_repair: invalid option -- 'h' Usage: xfs_repair [options] device Options: -f The device is a file -L Force log zeroing. Do this as a last resort. -l logdev Specifies the device where the external log resides. -m maxmem Maximum amount of memory to be used in megabytes. -n No modify mode, just checks the filesystem for damage. -P Disables prefetching. -r rtdev Specifies the device where the realtime section resides. -v Verbose output. -c subopts Change filesystem parameters - use xfs_admin. -o subopts Override default behaviour, refer to man page. -t interval Reporting interval in minutes. -d Repair dangerously. -V Reports version and exits.