From: fdmanana@kernel.org
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: [PATCH 0/4] btrfs: make test pass or skip them when using nodatacow
Date: Thu, 1 Feb 2024 18:03:46 +0000 [thread overview]
Message-ID: <cover.1706810184.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Several test btrfs test cases fail when using "-o nodatacow" in MOUNT_OPTIONS.
So fix that by either adapting the tests to pass or skip them if there's no
way for them to succeed in nodatacow mode.
Filipe Manana (4):
btrfs: require no nodatacow for tests that exercise compression
btrfs/173: make the test work when mounting with nodatacow
btrfs/299: skip test if we were mounted with nodatacow
btrfs: require no nodatacow for tests that exercise read repair
tests/btrfs/024 | 1 +
tests/btrfs/048 | 1 +
tests/btrfs/059 | 1 +
tests/btrfs/138 | 1 +
tests/btrfs/140 | 3 ++-
tests/btrfs/141 | 2 ++
tests/btrfs/157 | 2 ++
tests/btrfs/158 | 2 ++
tests/btrfs/173 | 5 +++++
tests/btrfs/215 | 2 ++
tests/btrfs/234 | 1 +
tests/btrfs/265 | 2 ++
tests/btrfs/266 | 2 ++
tests/btrfs/267 | 2 ++
tests/btrfs/268 | 2 ++
tests/btrfs/269 | 2 ++
tests/btrfs/281 | 1 +
tests/btrfs/289 | 2 ++
tests/btrfs/299 | 3 +++
19 files changed, 36 insertions(+), 1 deletion(-)
--
2.40.1
next reply other threads:[~2024-02-01 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 18:03 fdmanana [this message]
2024-02-01 18:03 ` [PATCH 1/4] btrfs: require no nodatacow for tests that exercise compression fdmanana
2024-02-01 18:03 ` [PATCH 2/4] btrfs/173: make the test work when mounting with nodatacow fdmanana
2024-02-05 12:26 ` David Disseldorp
2024-02-01 18:03 ` [PATCH 3/4] btrfs/299: skip test if we were mounted " fdmanana
2024-02-01 18:03 ` [PATCH 4/4] btrfs: require no nodatacow for tests that exercise read repair fdmanana
2024-02-05 12:29 ` [PATCH 0/4] btrfs: make test pass or skip them when using nodatacow David Disseldorp
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=cover.1706810184.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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