path: root/tests
diff options
authorQu Wenruo <>2018-04-03 13:39:47 +0800
committerDavid Sterba <>2018-04-24 13:00:11 +0200
commit5f53c23e7676e9fafb78fa166e3f00e143b5a2c5 (patch)
treea6039863b686c15610f82676274c97554e011883 /tests
parent2777e53911c51e33cf689eccab285ec557f13b12 (diff)
btrfs-progs: tests/fsck: Add test case to check if btrfs check can skip data csum verfication for metadata dump
Signed-off-by: Qu Wenruo <> Signed-off-by: David Sterba <>
Diffstat (limited to 'tests')
1 files changed, 30 insertions, 0 deletions
diff --git a/tests/fsck-tests/031-metadatadump-check-data-csum/ b/tests/fsck-tests/031-metadatadump-check-data-csum/
new file mode 100755
index 00000000..30b0b7a3
--- /dev/null
+++ b/tests/fsck-tests/031-metadatadump-check-data-csum/
@@ -0,0 +1,30 @@
+# To check if "btrfs check" can detect metadata dump (restored by btrfs-iamge)
+# and ignore --check-data-csum option
+source "$TEST_TOP/common"
+check_prereq btrfs
+check_prereq mkfs.btrfs
+check_prereq btrfs-image
+run_check $SUDO_HELPER "$TOP/mkfs.btrfs" -f "$TEST_DEV"
+run_check $SUDO_HELPER dd if=/dev/urandom of="$TEST_MNT/file" bs=4k count=16
+run_check $SUDO_HELPER "$TOP/btrfs-image" "$TEST_DEV" "restored_image"
+# use prepare_test_dev() to wipe all existing data on $TEST_DEV
+# so there is no way that restored image could have mathcing data csum
+run_check $SUDO_HELPER "$TOP/btrfs-image" -r "restored_image" "$TEST_DEV"
+# Should not report any error
+run_check "$TOP/btrfs" check --check-data-csum "$TEST_DEV"
+rm -rf -- "restored_image*"