From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Whitney <enwlinux@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: xfstests failures w/ metadata_csum
Date: Mon, 1 Dec 2014 12:20:45 -0800 [thread overview]
Message-ID: <20141201202045.GR10043@birch.djwong.org> (raw)
Hi Eric,
Could you remind me which xfstests are failing in 3.18-rc3+ with metadata_csum
enabled? I think you said generic/034, generic/321, and generic/322, but were
there more?
AFAICT the ext4 mount fails because it can't load the journal, and the journal
can't replay because jbd2_descr_block_csum_verify() fails; the 034 test appears
to drop all the writes related to the umount. recovery.c doesn't say anything
when the journal descriptor block fails csum verification, though it should.
Not sure why we end up with corrupt-looking descriptor blocks.
The reason why this appears in -rc3 is because that's when we added the patch
that forces journal_checksum on whenever metadata_csum is on, and I guess
few people were testing journal_checksum with xfstests before that.
--D
next reply other threads:[~2014-12-01 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 20:20 Darrick J. Wong [this message]
2014-12-01 22:02 ` xfstests failures w/ metadata_csum Darrick J. Wong
2014-12-01 22:05 ` Eric Whitney
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=20141201202045.GR10043@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=enwlinux@gmail.com \
--cc=linux-ext4@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).