From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org, dsterba@suse.cz
Cc: t-itoh@jp.fujitsu.com
Subject: [PATCH v2 3/3] btrfs-progs: convert-test: trigger chunk allocation after convert
Date: Thu, 15 Dec 2016 17:03:31 +0800 [thread overview]
Message-ID: <20161215090331.27486-4-quwenruo@cn.fujitsu.com> (raw)
In-Reply-To: <20161215090331.27486-1-quwenruo@cn.fujitsu.com>
Populate fs after convert so we can trigger data chunk allocation.
This can expose too restrict old rollback condition
Reported-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
tests/common | 4 ++++
tests/common.convert | 3 +++
2 files changed, 7 insertions(+)
diff --git a/tests/common b/tests/common
index 571118a..4a1330f 100644
--- a/tests/common
+++ b/tests/common
@@ -486,6 +486,10 @@ generate_dataset() {
run_check $SUDO_HELPER ln -s "$dirpath/$long_filename" "$dirpath/slow_slink.$num"
done
;;
+ large)
+ run_check $SUDO_HELPER dd if=/dev/urandom bs=32M count=1 \
+ of="$dirpath/$dataset_type" bs=32M >/dev/null 2>&1
+ ;;
esac
}
diff --git a/tests/common.convert b/tests/common.convert
index a2d3152..8c9242e 100644
--- a/tests/common.convert
+++ b/tests/common.convert
@@ -160,6 +160,9 @@ convert_test_post_checks_all() {
convert_test_post_check_checksums "$1"
convert_test_post_check_permissions "$2"
convert_test_post_check_acl "$3"
+
+ # Create a large file to trigger data chunk allocation
+ generate_dataset "large"
run_check_umount_test_dev
}
--
2.10.2
prev parent reply other threads:[~2016-12-15 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 9:03 [PATCH v2 0/3] Convert rollback rework for v4.9 Qu Wenruo
2016-12-15 9:03 ` [PATCH v2 1/3] btrfs-progs: file-item: Fix wrong file extents inserted Qu Wenruo
2016-12-15 9:03 ` [PATCH v2 2/3] btrfs-progs: convert: Rework rollback to handle new convert image Qu Wenruo
2016-12-16 6:11 ` Chandan Rajendra
2016-12-16 8:38 ` Qu Wenruo
2016-12-15 9:03 ` Qu Wenruo [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=20161215090331.27486-4-quwenruo@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=t-itoh@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).