From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: Fix qgroup false alerts on uninitialized rescan
Date: Thu, 26 Jul 2018 14:38:59 +0800 [thread overview]
Message-ID: <20180726063901.1252-1-wqu@suse.com> (raw)
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
qgroup-verify.c | 14 +++++++++++++-
.../no_rescan_kicked_in.img | Bin 0 -> 3072 bytes
.../fsck-tests/035-rescan-not-kicked-in/test.sh | 16 ++++++++++++++++
3 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 tests/fsck-tests/035-rescan-not-kicked-in/no_rescan_kicked_in.img
create mode 100755 tests/fsck-tests/035-rescan-not-kicked-in/test.sh
--
2.18.0
next reply other threads:[~2018-07-26 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 6:38 Qu Wenruo [this message]
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 ` [PATCH 0/2] btrfs-progs: Fix qgroup false alerts on uninitialized rescan 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=20180726063901.1252-1-wqu@suse.com \
--to=wqu@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).