From: Dave Chinner <***@redhat.com> We have had this code in the kernel for over a year now and have shaken all the known issues out of the code over the past few In fact using an external log will disable XFS' write barrier support.
Unmount and run xfs_repair kernel: XFS (dm-0): xfs_do_force_shutdown(0x8) called from line 1369 of file fs/xfs/xfs_buf.c. The device can be a regular file if the -f option is used. Unless you are experienced in debugging and repairing XFS file systems using xfs_db, it is recommended that you instead recreate the file system and restore its contents from a backup. xfs_logprint prints the log of an XFS filesystem (see xfs(5)).The device argument is the pathname of the partition or logical volume containing the filesystem. Return address = 0xffffffffa01efd4c kernel: XFS … The contents of the filesystem remain undisturbed. There are two major modes of operation in xfs_logprint.. One mode is better for filesystem operation debugging. Write barrier support is enabled by default in XFS since kernel version 2.6.17. It is disabled by mounting the filesystem with "nobarrier". Write barrier support. If the journal log has become corrupted, you can reset the log by specifying the -L option to xfs_repair. ファイルシステムをマウントすると XFS がLog inconsistent (didn't find previous header) メッセージを出力する Solution In Progress - Updated 2015-08-21T03:19:24+00:00 - Forces xfs_repair to zero the log even if it is dirty (contains metadata changes). This was caused by the log item size calculation return that there were no log vectors to write on a … When using this option the filesystem will likely appear to be corrupt, and can cause the loss of user files and/or data. XFS reports "Log inconsistent (didn't find previous header)" when trying to mount filesystem Solution Unverified - Updated 2016-11-03T03:24:52+00:00 - English Note: Resetting the log can leave the file system in an inconsistent state, resulting in data loss and data corruption. Barrier support will flush the write back cache at the appropriate times (such as on XFS log …