From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs-progs: fsck: fix false warning on sprouted filesystems
Date: Mon, 25 Apr 2022 19:06:34 +0200 [thread overview]
Message-ID: <20220425170634.GS18596@twin.jikos.cz> (raw)
In-Reply-To: <cover.1650180472.git.wqu@suse.com>
On Sun, Apr 17, 2022 at 03:30:34PM +0800, Qu Wenruo wrote:
> During my attempt to utilize seed device at mkfs time, I found there
> there is a small bug that btrfs check always reports devices size
> related warning on the sprouted device.
>
> It turns out we didn't iterate seed devices at all during btrfs check.
>
> The first patch will fix the problem and enhance the warning output.
> The second one will add a regression test for it.
>
> Qu Wenruo (2):
> btrfs-progs: check: fix wrong total bytes check for seed device
> btrfs-progs: fsck-tests: check warning for seed and sprouted
> filesystems
With the test fixups added to devel, thanks.
prev parent reply other threads:[~2022-04-25 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 7:30 [PATCH 0/2] btrfs-progs: fsck: fix false warning on sprouted filesystems Qu Wenruo
2022-04-17 7:30 ` [PATCH 1/2] btrfs-progs: check: fix wrong total bytes check for seed device Qu Wenruo
2022-04-17 9:33 ` Su Yue
2022-04-19 16:18 ` David Sterba
2022-04-17 7:30 ` [PATCH 2/2] btrfs-progs: fsck-tests: check warning for seed and sprouted filesystems Qu Wenruo
2022-04-25 17:04 ` David Sterba
2022-04-25 22:44 ` Qu Wenruo
2022-04-25 22:42 ` David Sterba
2022-04-25 23:06 ` Qu Wenruo
2022-04-25 23:15 ` David Sterba
2022-04-25 17:06 ` David Sterba [this message]
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=20220425170634.GS18596@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--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