From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 5/5] btrfs-progs: fsck-tests: add test case for init-csum-tree
Date: Mon, 17 Jan 2022 14:50:03 +0100 [thread overview]
Message-ID: <20220117135003.GH14046@twin.jikos.cz> (raw)
In-Reply-To: <550b61f3-2e3e-3c5a-17fa-0be8b63269bf@gmx.com>
On Sat, Jan 15, 2022 at 07:40:16AM +0800, Qu Wenruo wrote:
>
>
> On 2022/1/15 00:40, David Sterba wrote:
> > On Fri, Jan 14, 2022 at 08:51:23AM +0800, Qu Wenruo wrote:
> >> +run_check $SUDO_HELPER "$TOP/btrfs" check --force \
> >> + --init-csum-tree "$TEST_DEV"
> >> +
> >> +# No error should be found
> >> +run_check $SUDO_HELPER "$TOP/btrfs" check "$TEST_DEV"
> >> +btrfs ins dump-tree "$TEST_DEV" > /tmp/dump
> >
> > Is this some leftover from debugging?
>
> Oh, sorry.
>
> Mind to remove it when merging?
No.
next prev parent reply other threads:[~2022-01-17 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 0:51 [PATCH v2 0/5] btrfs-progs: check: properly generate csum for various complex combinations Qu Wenruo
2022-01-14 0:51 ` [PATCH v2 1/5] btrfs-progs: backref: properly queue indirect refs Qu Wenruo
2022-01-14 0:51 ` [PATCH v2 2/5] btrfs-progs: check: move csum tree population into mode-common.[ch] Qu Wenruo
2022-01-14 0:51 ` [PATCH v2 3/5] btrfs-progs: check: don't calculate csum for preallocated file extents Qu Wenruo
2022-01-14 0:51 ` [PATCH v2 4/5] btrfs-progs: check: handle csum generation properly for `--init-csum-tree --init-extent-tree` Qu Wenruo
2022-01-14 0:51 ` [PATCH v2 5/5] btrfs-progs: fsck-tests: add test case for init-csum-tree Qu Wenruo
2022-01-14 16:40 ` David Sterba
2022-01-14 23:40 ` Qu Wenruo
2022-01-17 13:50 ` David Sterba [this message]
2022-01-14 16:50 ` [PATCH v2 0/5] btrfs-progs: check: properly generate csum for various complex combinations David Sterba
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=20220117135003.GH14046@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.com \
/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).