From: Mark Harmstone <maharmstone@meta.com>
To: Filipe Manana <fdmanana@kernel.org>
Cc: "fstests@vger.kernel.org" <fstests@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: add test for missing csums in log when doing async on subpage vol
Date: Tue, 8 Oct 2024 14:06:39 +0000 [thread overview]
Message-ID: <ae203ea9-d5d4-4d25-825f-e017f23b3bf7@meta.com> (raw)
In-Reply-To: <CAL3q7H4oGiDQ4bahbJmxw9zp8CuzAF+VzJvqqdx10A8qyNk1Ag@mail.gmail.com>
Thanks Filipe.
On 8/10/24 14:35, Filipe Manana wrote:
>> +_begin_fstest auto quick metadata log volume
>
> Why the volume group? The test isn't doing any volume management stuff.
>
> However it should be in the "recoveryloop" group.
No worries, I'll change that.
>> +_log_writes_replay_log mkfs $SCRATCH_DEV
>> +
>> +_log_writes_fast_replay_check fua "$SCRATCH_DEV" "$BTRFS_UTIL_PROG check $SCRATCH_DEV"
>
> Why do we need to do the replays twice? Once with
> _log_writes_replay_log mkfs and then again with
> _log_writes_fast_replay_check fua.
_log_writes_replay_log mkfs to put the FS back how it was after
mkfs.btrfs, _log_writes_fast_replay_check to replay it from there. Is
_log_writes_replay_log redundant here?
> There's also nothing in this test that is btrfs specific, it could be
> made a generic test instead.
Yes there is, it's running btrfs check every time.
Mark
next prev parent reply other threads:[~2024-10-08 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 11:22 [PATCH] btrfs: add test for missing csums in log when doing async on subpage vol Mark Harmstone
2024-10-08 13:35 ` Filipe Manana
2024-10-08 14:06 ` Mark Harmstone [this message]
2024-10-08 14:18 ` Filipe Manana
2024-10-08 14:35 ` Mark Harmstone
2024-10-08 14:44 ` Filipe Manana
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=ae203ea9-d5d4-4d25-825f-e017f23b3bf7@meta.com \
--to=maharmstone@meta.com \
--cc=fdmanana@kernel.org \
--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