summaryrefslogtreecommitdiff
path: root/tests/test_config
diff options
context:
space:
mode:
authorTheodore Ts'o <tytso@mit.edu>2019-01-03 14:10:32 -0500
committerTheodore Ts'o <tytso@mit.edu>2019-01-03 14:10:32 -0500
commit877580939902798c959df0042a1843a3970a49c2 (patch)
treeada0c9c436026abe3020d4880618e73e7959306e /tests/test_config
parent112b38676bb47c1a6723eb01be7794ed564432a4 (diff)
downloade2fsprogs-877580939902798c959df0042a1843a3970a49c2.tar.gz
tests: generate test_data.tmp file from a script
Even if the debugfs executable is not sparse, it might contain a 1k aligned block which is all zeros, which when written into a 1k block file system by a test like d_loaddump will result in a sparse file and causing one or more test failures. Google-Bug-Id: 122085761 Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'tests/test_config')
-rw-r--r--tests/test_config7
1 files changed, 0 insertions, 7 deletions
diff --git a/tests/test_config b/tests/test_config
index 1f146ca2..9dc762ce 100644
--- a/tests/test_config
+++ b/tests/test_config
@@ -14,13 +14,6 @@ E2IMAGE_EXE="../misc/e2image"
DEBUGFS="$USE_VALGRIND ../debugfs/debugfs"
DEBUGFS_EXE="../debugfs/debugfs"
TEST_BITS="test_data.tmp"
-if [ ! -s $TEST_BITS ]; then
- # create a non-sparse test file if possible, since debugfs may be
- # sparse and cause "debugfs write" (using copy_file()) to skip holes
- # during testing if SEEK_DATA/SEEK_HOLE or FS_IOC_FIEMAP are available
- dd if=/dev/urandom of=$TEST_BITS bs=128k count=1 > /dev/null 2>&1 ||
- TEST_BITS="$DEFBUGFS_EXE"
-fi
RESIZE2FS_EXE="../resize/resize2fs"
RESIZE2FS="$USE_VALGRIND $RESIZE2FS_EXE"
E2UNDO_EXE="../misc/e2undo"