On Thu, May 17, 2018 at 10:12:11AM -0700, Darrick J. Wong wrote: > > It would seem that you've uncovered a log replay bug in xfs. :) .... > > > > [ 8201.588313] XFS (dm-0): metadata I/O error in "xlog_iodone" at daddr 0xf04fcc len 64 error 5 > > [ 8201.590504] XFS (dm-0): metadata I/O error in "xlog_iodone" at daddr 0xf00025 len 64 error 5 > > [ 8201.596839] XFS (dm-0): xfs_do_force_shutdown(0x2) called from line 1262 of file fs/xfs/xfs_log.c. Return address = 00000000755f7a21 > > [ 8201.597039] XFS (dm-0): Log I/O Error Detected. Shutting down filesystem Here's the important thing - a failed log write. > > > > *** xfs_logprint -t output *** > > > > Log inconsistent or not a log (last==0, first!=1) ISTR this implies the first checkpoint in the log is incomplete. i.e. we got a log IO error before an entire checkpoint was written and hence the log has a tail pointer of 0.... It might be worth cycling the mount before the test is run to see if that makes the problem go away (as there will be an unmount record already in the log and so when the test runs the last record to recover will not be 0.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
