From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: [PATCH 03/10] fstests: btrfs/022: Add extra qgroup verification after each work
Date: Tue, 29 Nov 2016 15:32:56 +0800 [thread overview]
Message-ID: <20161129073303.14776-4-quwenruo@cn.fujitsu.com> (raw)
In-Reply-To: <20161129073303.14776-1-quwenruo@cn.fujitsu.com>
The old code is using rescan to verify the number.
It will never hurt to add extra qgroup verification using btrfsck.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
tests/btrfs/022 | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/tests/btrfs/022 b/tests/btrfs/022
index 56d4f3d..d1ac921 100755
--- a/tests/btrfs/022
+++ b/tests/btrfs/022
@@ -125,20 +125,25 @@ _scratch_mkfs > /dev/null 2>&1
_scratch_mount
_basic_test
_scratch_unmount
+_btrfs_check_scratch_qgroup
_scratch_mkfs > /dev/null 2>&1
_scratch_mount
_rescan_test
_scratch_unmount
+_btrfs_check_scratch_qgroup
_scratch_mkfs > /dev/null 2>&1
_scratch_mount
_limit_test_exceed
_scratch_unmount
+_btrfs_check_scratch_qgroup
_scratch_mkfs > /dev/null 2>&1
_scratch_mount
_limit_test_noexceed
+_scratch_unmount
+_btrfs_check_scratch_qgroup
# success, all done
echo "Silence is golden"
--
2.7.4
next prev parent reply other threads:[~2016-11-29 7:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 7:32 [PATCH 00/10] Enhance btrfs qgroup test group coverage to support more mount options Qu Wenruo
2016-11-29 7:32 ` [PATCH 01/10] fstests: common: Introduce function to check qgroup correctness Qu Wenruo
2016-11-29 8:16 ` Eryu Guan
2016-11-29 8:44 ` Qu Wenruo
2016-11-29 21:01 ` Dave Chinner
2016-11-30 0:56 ` Qu Wenruo
2016-11-30 1:23 ` Dave Chinner
2016-11-29 7:32 ` [PATCH 02/10] fstests: btrfs/017: Use new _btrfs_check_scratch_qgroup function Qu Wenruo
2016-11-29 7:32 ` Qu Wenruo [this message]
2016-11-29 7:32 ` [PATCH 04/10] fstests: btrfs/028: Use new wrapped " Qu Wenruo
2016-11-29 7:32 ` [PATCH 05/10] fstests: btrfs/042: Add extra qgroup verification Qu Wenruo
2016-11-29 7:32 ` [PATCH 06/10] fstests: btrfs/091: Use _btrfs_check_scratch_qgroup other than fixed golden output Qu Wenruo
2016-11-29 7:33 ` [PATCH 07/10] fstests: btrfs/099: Add extra verification for qgroup Qu Wenruo
2016-11-29 7:33 ` [PATCH 08/10] fstests: btrfs/104: Use _btrfs_check_scratch_qgroup to replace open codes Qu Wenruo
2016-11-29 7:33 ` [PATCH 09/10] fstests: btrfs/122: Use _btrfs_check_scratch_qgroup to replace open code Qu Wenruo
2016-11-29 7:33 ` [PATCH 10/10] fstests: btrfs/123: " 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=20161129073303.14776-4-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=fstests@vger.kernel.org \
--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 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.