From: Eric Whitney <enwlinux@gmail.com>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: kvm-xfstests, adv test scenario, inode size-related failures
Date: Sun, 4 Sep 2022 16:09:53 -0400 [thread overview]
Message-ID: <YxUGEewB0AdMPTfl@debian-BULLSEYE-live-builder-AMD64> (raw)
Hi Ted:
I'm seeing a large number of test failures running 6.0-rc3 on the latest
version of the test appliance in the adv test scenario. All of these failures
share a common feature - mke2fs fails to create a scratch file system using the
inline option because the requested inode size is 128 bytes. This didn't
occur on the previous version of the test appliance.
It looks like /etc/mke2fs.conf contains an extra relation for the "small"
stanza: "inode_size = 128". This isn't present in mke2fs.conf in the
previous version of the test appliance, nor does it appear to be in the latest
master branch version of e2fsprogs (perhaps I'm looking in the wrong place).
Deleting that line from /etc/mke2fs.conf on the latest version of the test
appliance eliminates the failures (as does modifying ~/fs/ext4/conf/adv
to specify a 256 byte inode size in the list of mkfs options). The previous
version of the test appliance applied the default mke2fs.conf value of 256
for the inode size, so mke2fs didn't reject the request there.
For reference, the tests that fail for me include:
ext4/021, /036, /038, /039, /048, /271
generic/015, /077, /081, /083, /085, /204, /226, /250, /252, /371, /399, /416,
/427, /449, /459, /500, /511, /619, /626
shared/298
Eric
next reply other threads:[~2022-09-04 20:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 20:09 Eric Whitney [this message]
2022-09-05 14:59 ` kvm-xfstests, adv test scenario, inode size-related failures 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=YxUGEewB0AdMPTfl@debian-BULLSEYE-live-builder-AMD64 \
--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