Skip to contentSkip to conversation

btrfs-progs: fsck-tests: Move reloc tree images to 020-extent-ref-cases

PATCH Applied Qu Wenruo 2 participants 2 messages Dec 3, 2018 Btrfs file system

lore
Share & tools
lore

Qu Wenruo

author
#0 lore raw

PATCH 1/1 btrfs-progs: fsck-tests: Move reloc tree images to 020-extent-ref-cases

For reloc tree, despite of its short lifespan, it's still the backref, where reloc tree root backref points back to itself, makes it special.

So it's more approriate to put them into 020-extent-ref-cases.

Signed-off-by Qu Wenruo <[email protected]>
---
 tests/fsck-tests/015-tree-reloc-tree/test.sh    |  16 ----------------
 tests/fsck-tests/020-extent-ref-cases/test.sh   |   5 +++++
 .../tree_reloc_for_data_reloc.img.xz            | Bin
 .../tree_reloc_for_fs_tree.img.xz               | Bin
 4 files changed, 5 insertions(+), 16 deletions(-)
 delete mode 100755 tests/fsck-tests/015-tree-reloc-tree/test.sh
 rename tests/fsck-tests/{015-tree-reloc-tree => 020-extent-ref-cases}/tree_reloc_for_data_reloc.img.xz (100%)
 rename tests/fsck-tests/{015-tree-reloc-tree => 020-extent-ref-cases}/tree_reloc_for_fs_tree.img.xz (100%)
tests/fsck-tests/015-tree-reloc-tree/test.sh deleted +0 -16
deleted file mode 100755
index 5d9d5122fd06..000000000000
@@ -1,16 +0,0 @@
-#!/bin/bash
-# Make sure btrfs check won't report any false alerts for valid image with
-# reloc tree.
-#
-# Also due to the short life span of reloc tree, save the as dump example for
-# later usage.
-
-source "$TEST_TOP/common"
-
-check_prereq btrfs
-
-check_image() {
-	run_check "$TOP/btrfs" check "$1"
-}
-
-check_all_images
tests/fsck-tests/020-extent-ref-cases/test.sh +5 -0
index a1bf75b14486..2f5a05cca4d4 100755
@@ -14,6 +14,11 @@
 #   Containing a block group and its first extent at
 #   the beginning of leaf.
 #   Which caused false alert for lowmem mode.
+#
+# Special cases with some rare backref type
+# * reloc tree
+#   For both fs tree and data reloc tree.
+#   Special for its backref pointing to itself and its short life span.
 
 source "$TEST_TOP/common"
tests/fsck-tests/020-extent-ref-cases/tree_reloc_for_data_reloc.img.xz renamed from tests/fsck-tests/015-tree-reloc-tree/tree_reloc_for_data_reloc.img.xz +0 -0
similarity index 100%
rename from tests/fsck-tests/015-tree-reloc-tree/tree_reloc_for_data_reloc.img.xz
rename to tests/fsck-tests/020-extent-ref-cases/tree_reloc_for_data_reloc.img.xz
tests/fsck-tests/020-extent-ref-cases/tree_reloc_for_fs_tree.img.xz renamed from tests/fsck-tests/015-tree-reloc-tree/tree_reloc_for_fs_tree.img.xz +0 -0
similarity index 100%
rename from tests/fsck-tests/015-tree-reloc-tree/tree_reloc_for_fs_tree.img.xz
rename to tests/fsck-tests/020-extent-ref-cases/tree_reloc_for_fs_tree.img.xz
Signature · 1 line
2.19.2
Applied
#1 lore raw
Quoted 6 lines · Qu Wenruo

For reloc tree, despite of its short lifespan, it's still the backref, where reloc tree root backref points back to itself, makes it special.

So it's more approriate to put them into 020-extent-ref-cases.

Signed-off-by Qu Wenruo <[email protected]>

Applied, thanks.