Files
apfstests/tests/generic/042
T
Eryu Guan 11a3e8bd82 generic: require journal in shutdown tests
Tests in shutdown group are supposed to test journal recovery after
filesystem shutdown, and the tests assume the filesystem in test has
journal support. But with the ext4 shutdown function added in
4.11-rc kernel, ext2 gains shutdown support too when driving with
ext4 driver, so generic/051 fails because fs corruption after test.

Adding _require_metadata_journaling to all generic tests in shutdown
group to ensure there's journal present.

generic/050 is skipped because it has _require_scratch_nocheck,
which indicates no fsck is done after test.

Reviewed-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Eryu Guan <eguan@redhat.com>
2017-03-09 15:01:43 +08:00

104 lines
2.7 KiB
Bash
Executable File

#! /bin/bash
# FS QA Test No. 042
#
# Test stale data exposure via writeback using various file allocation
# modification commands. The presumption is that such commands result in partial
# writeback and can convert a delayed allocation extent, that might be larger
# than the ranged affected by fallocate, to a normal extent. If the fs happens
# to crash sometime between when the extent modification is logged and writeback
# occurs for dirty pages within the extent but outside of the fallocated range,
# stale data exposure can occur.
#
#-----------------------------------------------------------------------
# Copyright (c) 2014 Red Hat, Inc. All Rights Reserved.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it would be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write the Free Software Foundation,
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
#-----------------------------------------------------------------------
#
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
here=`pwd`
tmp=/tmp/$$
status=1 # failure is the default!
trap "_cleanup; exit \$status" 0 1 2 3 15
_cleanup()
{
cd /
rm -f $tmp.*
}
# get standard environment, filters and checks
. ./common/rc
. ./common/filter
. ./common/punch
# real QA test starts here
rm -f $seqres.full
_crashtest()
{
cmd=$1
img=$SCRATCH_MNT/$seq.img
mnt=$SCRATCH_MNT/$seq.mnt
file=$mnt/file
# Create an fs on a small, initialized image. The pattern is written to
# the image to detect stale data exposure.
$XFS_IO_PROG -f -c "truncate 0" -c "pwrite 0 25M" $img \
>> $seqres.full 2>&1
_mkfs_dev $img >> $seqres.full 2>&1
mkdir -p $mnt
_mount $img $mnt
echo $cmd
# write, run the test command and shutdown the fs
$XFS_IO_PROG -f -c "pwrite -S 1 0 64k" -c "$cmd 60k 4k" $file | \
_filter_xfs_io
./src/godown -f $mnt
$UMOUNT_PROG $mnt
_mount $img $mnt
# we generally expect a zero-sized file (this should be silent)
hexdump $file
$UMOUNT_PROG $mnt
}
# Modify as appropriate.
_supported_fs generic
_supported_os Linux
_require_scratch
_require_scratch_shutdown
_require_xfs_io_command "falloc"
_require_xfs_io_command "fpunch"
_require_xfs_io_command "fzero"
_scratch_mkfs >/dev/null 2>&1
_require_metadata_journaling $SCRATCH_DEV
_scratch_mount
_crashtest "falloc -k"
_crashtest "fpunch"
_crashtest "fzero -k"
status=0
exit