From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Zorro Lang <zlang@redhat.com>, fstests@vger.kernel.org
Subject: Re: Problems about xfstests g/475
Date: Fri, 18 May 2018 14:14:32 +1000 [thread overview]
Message-ID: <20180518041431.GL23861@dastard> (raw)
In-Reply-To: <20180517171211.GF4910@magnolia>
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@fromorbit.com
prev parent reply other threads:[~2018-05-18 4:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 9:03 Problems about xfstests g/475 Zorro Lang
2018-05-17 14:30 ` Darrick J. Wong
2018-05-17 15:45 ` Zorro Lang
2018-05-17 17:12 ` Darrick J. Wong
2018-05-17 18:21 ` Zorro Lang
2018-05-18 4:14 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180518041431.GL23861@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=zlang@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox