From: Zorro Lang <zlang@redhat.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, fstests@vger.kernel.org,
tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCHSET 0/3] fstests: refactor ext4-specific code
Date: Sat, 6 Aug 2022 22:36:06 +0800 [thread overview]
Message-ID: <20220806143606.kd7ikbdjntugcpp4@zlang-mailbox> (raw)
In-Reply-To: <165950050051.198922.13423077997881086438.stgit@magnolia>
On Tue, Aug 02, 2022 at 09:21:40PM -0700, Darrick J. Wong wrote:
> Hi all,
>
> This series aims to make it so that fstests can install device mapper
> filters for external log devices. Before we can do that, however, we
> need to change fstests to pass the device path of the jbd2 device to
> mount and mkfs. Before we can do /that/, refactor all the ext4-specific
> code out of common/rc into a separate common/ext4 file.
>
> If you're going to start using this mess, you probably ought to just
> pull from my git trees, which are linked below.
>
> This is an extraordinary way to destroy everything. Enjoy!
> Comments and questions are, as always, welcome.
>
> --D
>
> fstests git tree:
> https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=refactor-ext4-helpers
> ---
Hi Darrick,
There're 3 failures[1] if test ext4 with external logdev, after merging this
patchset.
The g/629 is always failed with or without this patchset, it fails if test
with external logdev.
The g/250 and g/252 fail due to _scratch_mkfs_sized doesn't use common ext4
mkfs helper, so can't deal with SCRATCH_LOGDEV well.
Thanks,
Zorro
[1]
SECTION -- logdev
FSTYP -- ext4
PLATFORM -- Linux/x86_64 hp-dl380pg8-01 5.19.0-0.rc2.21.fc37.x86_64+debug #1 SMP PREEMPT_DYNAMIC Mon Jun 13 14:55:18 UTC 2022
MKFS_OPTIONS -- -F -J device=/dev/loop0 /dev/sda3
MOUNT_OPTIONS -- -o acl,user_xattr -o context=system_u:object_r:root_t:s0 -o journal_path=/dev/loop0 /dev/sda3 /mnt/scratch
generic/250 2s ... - output mismatch (see /root/git/xfstests/results//logdev/generic/250.out.bad)
--- tests/generic/250.out 2022-04-29 23:07:23.262498285 +0800
+++ /root/git/xfstests/results//logdev/generic/250.out.bad 2022-08-06 22:26:45.179294149 +0800
@@ -1,9 +1,19 @@
QA output created by 250
Format and mount
+umount: /mnt/scratch: not mounted.
+mount: /mnt/scratch: wrong fs type, bad option, bad superblock on /dev/mapper/error-test, missing codepage or helper program, or other error.
+ dmesg(1) may have more information after failed mount system call.
Create the original files
+umount: /mnt/scratch: not mounted.
...
(Run 'diff -u /root/git/xfstests/tests/generic/250.out /root/git/xfstests/results//logdev/generic/250.out.bad' to see the entire diff)
generic/252 2s ... - output mismatch (see /root/git/xfstests/results//logdev/generic/252.out.bad)
--- tests/generic/252.out 2022-04-29 23:07:23.264498308 +0800
+++ /root/git/xfstests/results//logdev/generic/252.out.bad 2022-08-06 22:26:48.495330525 +0800
@@ -1,10 +1,19 @@
QA output created by 252
Format and mount
+umount: /mnt/scratch: not mounted.
+mount: /mnt/scratch: wrong fs type, bad option, bad superblock on /dev/mapper/error-test, missing codepage or helper program, or other error.
+ dmesg(1) may have more information after failed mount system call.
Create the original files
+umount: /mnt/scratch: not mounted.
...
(Run 'diff -u /root/git/xfstests/tests/generic/252.out /root/git/xfstests/results//logdev/generic/252.out.bad' to see the entire diff)
generic/629 3s ... - output mismatch (see /root/git/xfstests/results//logdev/generic/629.out.bad)
--- tests/generic/629.out 2022-04-29 23:07:23.545501491 +0800
+++ /root/git/xfstests/results//logdev/generic/629.out.bad 2022-08-06 22:26:50.810355920 +0800
@@ -1,4 +1,5 @@
QA output created by 629
+mke2fs 1.46.5 (30-Dec-2021)
test o_sync write
310f146ce52077fcd3308dcbe7632bb2 SCRATCH_MNT/0
test unaligned copy range o_sync
...
(Run 'diff -u /root/git/xfstests/tests/generic/629.out /root/git/xfstests/results//logdev/generic/629.out.bad' to see the entire diff)
Ran: generic/250 generic/252 generic/629
Failures: generic/250 generic/252 generic/629
Failed 3 of 3 tests
> common/config | 4 +
> common/ext4 | 176 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> common/rc | 177 ++-------------------------------------------------------
> common/xfs | 23 +++++++
> 4 files changed, 208 insertions(+), 172 deletions(-)
> create mode 100644 common/ext4
>
next prev parent reply other threads:[~2022-08-06 14:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 4:21 [PATCHSET 0/3] fstests: refactor ext4-specific code Darrick J. Wong
2022-08-03 4:21 ` [PATCH 1/3] common/rc: move ext4-specific helpers into a separate common/ext4 file Darrick J. Wong
2022-08-03 4:21 ` [PATCH 2/3] common/rc: move XFS-specific parts of _scratch_options into common/xfs Darrick J. Wong
2022-08-03 4:21 ` [PATCH 3/3] common/ext4: provide custom ext4 scratch fs options Darrick J. Wong
2022-08-03 18:28 ` Zorro Lang
2022-08-03 18:52 ` Darrick J. Wong
2022-08-04 0:25 ` [PATCH v1.2 " Darrick J. Wong
2022-08-04 5:03 ` Darrick J. Wong
2022-08-04 16:29 ` [PATCH v1.3 " Darrick J. Wong
2022-08-05 17:08 ` Zorro Lang
2022-08-06 14:36 ` Zorro Lang [this message]
2022-08-07 16:30 ` [PATCHSET 0/3] fstests: refactor ext4-specific code Darrick J. Wong
2022-08-08 15:13 ` Zorro Lang
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=20220806143606.kd7ikbdjntugcpp4@zlang-mailbox \
--to=zlang@redhat.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-xfs@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).