From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/3] btrfs-progs: btrfs-progs: csum-change enhancement
Date: Fri, 21 Jun 2024 14:46:53 +0930 [thread overview]
Message-ID: <cover.1718946934.git.wqu@suse.com> (raw)
[CHANGELOG]
v2:
- Enhance the error injection detection
Now instead of plain run_mustfail, we do check both the failure and
the stderr.
Only when the csum-change failed and stderr includes the injection
cookie output, we know it's really the injection causing error.
The first two patches are small enhancement and bugfix:
- Fix a missing error handling
- Do multi-transaction csum deletion and rename
Or we can generate GiB or even TiB level of dirty metadata.
Finally introduce a basic error injection based test case, which will:
- Check if we have error injection first
- Inject error at the end of data csum generation
- Make sure resume from above situation is correct
I'm not adding extra injections because I believe there would definitely
be corner cases that need to be fixed.
Qu Wenruo (3):
btrfs-progs: csum-change: add error handling for search old csums
btrfs-progs: csum-change: add leaf based threshold
btrfs-progs: misc-tests: add a basic resume test using error injection
.../065-csum-conversion-inject/test.sh | 61 +++++++++++++++
tune/change-csum.c | 75 +++++++++++++++----
2 files changed, 120 insertions(+), 16 deletions(-)
create mode 100755 tests/misc-tests/065-csum-conversion-inject/test.sh
--
2.45.2
next reply other threads:[~2024-06-21 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 5:16 Qu Wenruo [this message]
2024-06-21 5:16 ` [PATCH v2 1/3] btrfs-progs: csum-change: add error handling for search old csums Qu Wenruo
2024-06-21 5:16 ` [PATCH v2 2/3] btrfs-progs: csum-change: add leaf based threshold Qu Wenruo
2024-06-21 5:16 ` [PATCH v2 3/3] btrfs-progs: misc-tests: add a basic resume test using error injection Qu Wenruo
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.1718946934.git.wqu@suse.com \
--to=wqu@suse.com \
--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