From: Eric Whitney <enwlinux@gmail.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: e2fsprogs maint branch and metadata_csum option
Date: Mon, 7 Jan 2013 13:03:52 -0500 [thread overview]
Message-ID: <20130107180352.GA18255@wallace> (raw)
In today's concall, I reported an e2fsprogs maint branch test failure I'd
just seen with Ted's xfstests-bld harness. When running the
metadata_csum,64bit scenario, the result was an immediate mkfs failure with
the following diagnostic: Invalid filesystem option set: metadata_csum,64bit
The metadata_csum option alone was enough to trigger the error. However, a
look at the maint branch code suggests that it doesn't contain the
metadata_csum support found in the master branch. I'm guessing my
expectations about the current state of the maint branch were wrong and that
we'll pick up the metadata_csum feature on the merge to master?
If so, there's no bug here - sorry for the noise.
Thanks,
Eric
next reply other threads:[~2013-01-07 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 18:03 Eric Whitney [this message]
2013-01-07 18:53 ` e2fsprogs maint branch and metadata_csum option Theodore Ts'o
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=20130107180352.GA18255@wallace \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).