From: Frederick Lawler <fred@cloudflare.com>
To: amir73il@gmail.com, mcgrof@kernel.org
Cc: kdevops@lists.linux.dev, kernel-team@cloudflare.com,
linux-fsdevel@vger.kernel.org,
Frederick Lawler <fred@cloudflare.com>
Subject: [RFC PATCH kdevops 0/2] augment expunge list for v6.1.53
Date: Fri, 15 Sep 2023 18:48:55 -0500 [thread overview]
Message-ID: <20230915234857.1613994-1-fred@cloudflare.com> (raw)
In an effort to test and prepare patches from XFS to stable 6.1.y [1], I needed
to make a baseline for v6.1.53 to verify that the backported patches do not
introduce regressions (if any). However, after a 'make fstests-baseline', we
observed that compared to v6.1.42, v6.1.53 introduced more than expected
expunges to XFS. This RFC is an attempt to put some eyes to this and open up a
discussion.
At Cloudflare, the Linux team does not have an easy way to obtain dedicated and
easily configurable server infrastructure to execute kdevops filesystem testing,
but we do have an easily-configurable kubernetes infrastructure. I prepared a
POC to spin up virtual machines [2] in kubernetes to emulate what terraform
may do for OpenStack, Azure, AWS, etc... to perform this test. Therefore, the
configuration option is set to SKIP_BRINGUP=y
In this baseline, I spun up XFS workflow nodes for:
- xfs_crc
- xfs_logdev
- xfs_nocrc
- xfs_nocrc_512
- xfs_reflink
- xfs_reflink_1024
- xfs_reflink_normapbt
- xfs_rtdev
Each node is running a vanilla-stable 6.1.y (6.1.53), and the image is based on
latest Debian SID [3]. Each node also has its own dedicated /data and /media
partitions to store Linux, fstests, etc... and sparse-images respectfully.
In v6.1.42, we don't currently have expunges for xfs_reflink_normapbt, and
xfs_reflink. So those are _new_. The rest had significant additions. However,
not all nodes finished their testing after >12hrs of run time. Some appeared to
be stuck, in particular xfs_rtdev, and never finished (reason unknown).
I CTRL+C and ran 'make fstests-results'.
I prepared a fork [4] where the results 6.1.53.xz can be found.
These patches are based on top of commit 0ec98182f4a9 ("bootlinux/fstests:
remove odd hplip user")
Links:
1: https://lore.kernel.org/all/CAOQ4uxgvawD4=4g8BaRiNvyvKN1oreuov_ie6sK6arq3bf8fxw@mail.gmail.com/
2: https://kubevirt.io/api-reference/v1.0.0/definitions.html#_v1_virtualmachine
3: https://cloud.debian.org/images/cloud/sid/daily/latest/ (debian-sid-genericcloud-amd64-daily.qcow2)
4: https://github.com/fredlawl/kdevops/commit/afcb8fe7c4498d2be5386e191db3534f651a3730#diff-0677846133ad9128bf752f674b3c8da437c12ce28f48d8890b9f66d0dcb3717c
Frederick Lawler (2):
fstests/xfs: copy 6.1.42 baseline for v6.1.53
xfs: merge common expunge lists for v6.1.53
.../expunges/6.1.53/btrfs/unassigned/all.txt | 38 +++++++++++
.../btrfs/unassigned/btrfs_noraid56.txt | 2 +
.../6.1.53/btrfs/unassigned/btrfs_simple.txt | 2 +
.../btrfs/unassigned/btrfs_simple_zns.txt | 65 +++++++++++++++++++
.../expunges/6.1.53/ext4/unassigned/all.txt | 21 ++++++
.../unassigned/ext4_advanced_features.txt | 1 +
.../6.1.53/ext4/unassigned/ext4_defaults.txt | 5 ++
.../expunges/6.1.53/xfs/unassigned/all.txt | 40 ++++++++++++
.../6.1.53/xfs/unassigned/xfs_crc.txt | 7 ++
.../6.1.53/xfs/unassigned/xfs_logdev.txt | 26 ++++++++
.../6.1.53/xfs/unassigned/xfs_nocrc.txt | 7 ++
.../6.1.53/xfs/unassigned/xfs_nocrc_512.txt | 12 ++++
.../6.1.53/xfs/unassigned/xfs_reflink.txt | 5 ++
.../xfs/unassigned/xfs_reflink_1024.txt | 12 ++++
.../xfs/unassigned/xfs_reflink_normapbt.txt | 10 +++
.../6.1.53/xfs/unassigned/xfs_rtdev.txt | 49 ++++++++++++++
16 files changed, 302 insertions(+)
create mode 100644 workflows/fstests/expunges/6.1.53/btrfs/unassigned/all.txt
create mode 100644 workflows/fstests/expunges/6.1.53/btrfs/unassigned/btrfs_noraid56.txt
create mode 100644 workflows/fstests/expunges/6.1.53/btrfs/unassigned/btrfs_simple.txt
create mode 100644 workflows/fstests/expunges/6.1.53/btrfs/unassigned/btrfs_simple_zns.txt
create mode 100644 workflows/fstests/expunges/6.1.53/ext4/unassigned/all.txt
create mode 100644 workflows/fstests/expunges/6.1.53/ext4/unassigned/ext4_advanced_features.txt
create mode 100644 workflows/fstests/expunges/6.1.53/ext4/unassigned/ext4_defaults.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/all.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_crc.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_logdev.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_nocrc.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_nocrc_512.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_reflink.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_reflink_1024.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_reflink_normapbt.txt
create mode 100644 workflows/fstests/expunges/6.1.53/xfs/unassigned/xfs_rtdev.txt
--
2.34.1
next reply other threads:[~2023-09-15 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 23:48 Frederick Lawler [this message]
2023-09-15 23:48 ` [RFC PATCH kdevops 1/2] fstests/xfs: copy 6.1.42 baseline for v6.1.53 Frederick Lawler
2023-09-15 23:48 ` [RFC PATCH kdevops 2/2] xfs: merge common expunge lists " Frederick Lawler
2023-09-16 9:23 ` [RFC PATCH kdevops 0/2] augment expunge list " Amir Goldstein
2023-09-18 18:52 ` Luis Chamberlain
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=20230915234857.1613994-1-fred@cloudflare.com \
--to=fred@cloudflare.com \
--cc=amir73il@gmail.com \
--cc=kdevops@lists.linux.dev \
--cc=kernel-team@cloudflare.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mcgrof@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 read-only IMAP folder(s) and NNTP newsgroup(s).