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: Fix qgroup false alerts on uninitialized rescan
Date: Fri, 3 Aug 2018 16:58:28 +0200 [thread overview]
Message-ID: <20180803145828.GZ3218@twin.jikos.cz> (raw)
In-Reply-To: <20180726063901.1252-1-wqu@suse.com>
On Thu, Jul 26, 2018 at 02:38:59PM +0800, Qu Wenruo wrote:
> This patches can be fetched from github:
> https://github.com/adam900710/btrfs-progs/tree/qgroup_report
>
> It's possible that certain timed power loss could lead to initialized quota
> tree without rescan kicked in.
> Can be reproduced in btrfs/166 with low possibility.
>
> In that case, since default flags for QUOTA_STATUS is ON|INCONSISTENT,
> btrfs check will still check qgroups and report difference as error.
>
> However rescan progress of QUOTA_STATUS is still 0, means qgroup rescan
> hasn't been kicked in, and all quota numbers are 0, difference is
> expected.
>
> In this case, make btrfs check don't report such uninitialized rescan as
> error.
>
> Qu Wenruo (2):
> btrfs-progs: qgroup-verify: Don't treat qgroup difference as error if
> the fs hasn't initialized a rescan
> btrfs-progs: fsck-tests: Add test image to check if btrfs check
> reports uninitialized rescan as error
Applied, thanks.
prev parent reply other threads:[~2018-08-03 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 6:38 [PATCH 0/2] btrfs-progs: Fix qgroup false alerts on uninitialized rescan Qu Wenruo
2018-07-26 6:39 ` [PATCH 1/2] btrfs-progs: qgroup-verify: Don't treat qgroup difference as error if the fs hasn't initialized a rescan Qu Wenruo
2018-07-26 6:39 ` [PATCH 2/2] btrfs-progs: fsck-tests: Add test image to check if btrfs check reports uninitialized rescan as error Qu Wenruo
2018-08-03 14:58 ` 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=20180803145828.GZ3218@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 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.