| Message ID | 20200117072959.27929-4-wqu@suse.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | btrfs-progs: Do proper extent item generation repair | expand |
diff --git a/tests/fsck-tests/044-invalid-extent-item-generation/.lowmem_repairable b/tests/fsck-tests/044-invalid-extent-item-generation/.lowmem_repairable new file mode 100644 index 000000000000..e69de29bb2d1 diff --git a/tests/fsck-tests/044-invalid-extent-item-generation/test.sh b/tests/fsck-tests/044-invalid-extent-item-generation/test.sh deleted file mode 100755 index 2b88a3c7b3bb..000000000000 --- a/tests/fsck-tests/044-invalid-extent-item-generation/test.sh +++ /dev/null @@ -1,19 +0,0 @@ -#!/bin/bash -# -# Due to a bug in --init-extent-tree option, we may create bad generation -# number for data extents. -# -# This test case will ensure btrfs check can at least detect such problem, -# just like kernel tree-checker. - -source "$TEST_TOP/common" - -check_prereq btrfs - -check_image() { - run_mustfail \ - "btrfs check failed to detect invalid extent item generation" \ - "$TOP/btrfs" check "$1" -} - -check_all_images
Since both original and lowmem mode can repair it, make that test case to cover both detection and repair. Signed-off-by: Qu Wenruo <wqu@suse.com> --- .../.lowmem_repairable | 0 .../test.sh | 19 ------------------- 2 files changed, 19 deletions(-) create mode 100644 tests/fsck-tests/044-invalid-extent-item-generation/.lowmem_repairable delete mode 100755 tests/fsck-tests/044-invalid-extent-item-generation/test.sh