c/mirror_zfs
1
0
Fork 0
mirror of https://git.proxmox.com/git/mirror_zfs.git synced 2026-05-30 18:56:23 +03:00
Code Issues Packages Projects Releases Wiki Activity

ZTS: Introduce targeted corruption in file blocks

Browse Source 
filetest_001_pos verifies that various checksum algorithms detect
corruption by overwriting the underlying vdev on which a file resides.
It is possible for the overwrite to miss the blocks of a file, causing a
spurious failure. This change introduces a function to corrupt the
individual blocks of a file as determined by zdb.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Reviewed-by: Ryan Moeller <ryan@ixsystems.com>
Signed-off-by: John Kennedy <john.kennedy@delphix.com>
Closes #9288
This commit is contained in:
John Wren Kennedy
2019-09-09 17:11:07 -06:00
committed by Brian Behlendorf
parent 43f4495bde
commit b63e2d881f
2 changed files with 96 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/zfs-tests/tests/functional/checksum/filetest_001_pos.ksh
+9 -18
View File
@@ -21,7 +21,7 @@
#
#
# Copyright (c) 2018 by Delphix. All rights reserved.
# Copyright (c) 2018, 2019 by Delphix. All rights reserved.
#
. $STF_SUITE/include/libtest.shlib
@@ -32,8 +32,8 @@
# Sanity test to make sure checksum algorithms work.
# For each checksum, create a file in the pool using that checksum. Verify
# that there are no checksum errors. Next, for each checksum, create a single
# file in the pool using that checksum, scramble the underlying vdev, and
# verify that we correctly catch the checksum errors.
# file in the pool using that checksum, corrupt the file, and verify that we
# correctly catch the checksum errors.
#
# STRATEGY:
# Test 1
@@ -46,11 +46,9 @@
# Test 2
# 6. For each checksum:
# 7. Create a file using the checksum
# 8. Export the pool
# 9. Scramble the data on one of the underlying VDEVs
# 10. Import the pool
# 11. Scrub the pool
# 12. Verify that there are checksum errors
# 8. Corrupt all level 0 blocks in the file
# 9. Scrub the pool
# 10. Verify that there are checksum errors
verify_runnable "both"
@@ -66,8 +64,6 @@ log_assert "Create and read back files with using different checksum algorithms"
log_onexit cleanup
WRITESZ=1048576
SKIPCNT=$(((4194304 / $WRITESZ) * 2))
WRITECNT=$((($MINVDEVSIZE / $WRITESZ) - $SKIPCNT))
# Get a list of vdevs in our pool
set -A array $(get_disklist_fullpath)
@@ -96,7 +92,7 @@ log_must [ $cksum -eq 0 ]
rm -fr $TESTDIR/*
log_assert "Test scrambling the disk and seeing checksum errors"
log_assert "Test corrupting the files and seeing checksum errors"
typeset -i j=1
while [[ $j -lt ${#CHECKSUM_TYPES[*]} ]]; do
type=${CHECKSUM_TYPES[$j]}
@@ -104,14 +100,9 @@ while [[ $j -lt ${#CHECKSUM_TYPES[*]} ]]; do
log_must file_write -o overwrite -f $TESTDIR/test_$type \
-b $WRITESZ -c 5 -d R
log_must zpool export $TESTPOOL
# Corrupt the level 0 blocks of this file
corrupt_blocks_at_level $TESTDIR/test_$type
# Scramble the data on the first vdev in our pool. Skip the first
# and last 16MB of data, then scramble the rest after that.
log_must dd if=/dev/zero of=$firstvdev bs=$WRITESZ skip=$SKIPCNT \
count=$WRITECNT
log_must zpool import $TESTPOOL
log_must zpool scrub $TESTPOOL
log_must wait_scrubbed $TESTPOOL