From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Nikolay Borisov <nborisov@suse.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: do not allow setting seed flag on fs with dirty log
Date: Mon, 18 Apr 2022 14:58:46 +0300 [thread overview]
Message-ID: <9db93422-18d8-9978-3247-b90e0fd8717e@suse.com> (raw)
In-Reply-To: <b8438797-164e-989a-6fad-5dc15568ecb8@gmx.com>
On 18.04.22 г. 9:44 ч., Qu Wenruo wrote:
> y way to create a dirty journal.
>
> But I'm not sure if btrfs-progs really wants a complicated dm based
> solution to do the same thing.
>
> Or maybe I can just use an raw image for that?
It doesn't matter what way you use to create the journal, what's
important is that you have a dirty journal and verify a particular
functionality involving it. You can either encode the steps to create
the dirty journal image in the test itself, or simply provide an image
with a dirty journal.
next prev parent reply other threads:[~2022-04-18 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 11:37 [PATCH] btrfs-progs: do not allow setting seed flag on fs with dirty log Qu Wenruo
2022-04-18 6:41 ` Nikolay Borisov
2022-04-18 6:44 ` Qu Wenruo
2022-04-18 11:58 ` Nikolay Borisov [this message]
2022-04-18 15:30 ` Josef Bacik
2022-04-18 23:31 ` Qu Wenruo
2022-04-19 12:07 ` Anand Jain
2022-04-19 12:10 ` 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=9db93422-18d8-9978-3247-b90e0fd8717e@suse.com \
--to=nborisov@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.