From: Sweet Tea Dorminy <sweettea@permabit.com>
To: linux-xfs@vger.kernel.org
Subject: XFS journal write ordering constraints?
Date: Thu, 8 Jun 2017 11:42:11 -0400 [thread overview]
Message-ID: <CALoZfD4-uqhRSfEh0Y+v8jjSDY2KkAh-hhwdLnRgZopHEETUXA@mail.gmail.com> (raw)
Greetings;
When using XFS with a 1k block size atop our device, we regularly get
"log record CRC mismatch"es when mounting XFS after a crash, and we
are attempting to understand why. We are using RHEL7.3 with its kernel
3.10.0-514.10.2.el7.x86_64, xfsprogs version 4.5.0.
Tracing indicates the following situation occurs:
Some pair of consecutive locations contains data A1 and B1, respectively.
The XFS journal issues new writes to those locations,
containing data A2 and B2.
The write of B' finishes, but A' is still outstanding at the
time of the crash.
Crash occurs. The data on disk is A1 and B2, respectively.
XFS fails to mount, complaining that the checksum mismatches.
Does XFS expect sequentially issued journal IO to be committed to disk
in the order of issuance due to the use of FUA?
Thanks!
Sweet Tea Dorminy
Permabit Technology Corporation
Cambridge, MA
next reply other threads:[~2017-06-08 15:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 15:42 Sweet Tea Dorminy [this message]
2017-06-09 12:38 ` XFS journal write ordering constraints? Brian Foster
2017-06-09 17:30 ` Brian Foster
2017-06-09 23:44 ` Dave Chinner
2017-06-10 2:06 ` Sweet Tea Dorminy
2017-06-12 14:55 ` Brian Foster
2017-06-12 16:18 ` Brian Foster
2017-06-15 22:28 ` Sweet Tea Dorminy
2017-06-16 13:42 ` Brian Foster
2017-06-12 23:50 ` Dave Chinner
2017-06-13 14:14 ` Sweet Tea Dorminy
2017-06-13 22:16 ` Dave Chinner
2017-06-14 6:46 ` Christoph Hellwig
2017-06-13 16:29 ` Brian Foster
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=CALoZfD4-uqhRSfEh0Y+v8jjSDY2KkAh-hhwdLnRgZopHEETUXA@mail.gmail.com \
--to=sweettea@permabit.com \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).