mirror of
https://github.com/linux-apfs/apfstests.git
synced 2026-05-01 15:01:44 -07:00
Naohiro Aota
74e99aebdc
Many test cases use xfs_io -c 'falloc' but forgot to add _require_xfs_io_command "falloc". This will fail the test case if we run the test case on a file system without fallcoate support e.g. F2FS. While we believe that normal fallocate(mode = 0) is always supported on Linux, it is not true. Fallocate is disabled in several implementations of zoned block support for file systems because the pre-allocated region will break the sequential writing rule. Currently, several test cases unconditionally call fallocate(). Let's add _require_xfs_io_command "falloc" to properly check the feature is supported by a testing file system. Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com> Reviewed-by: Eryu Guan <guaneryu@gmail.com> Signed-off-by: Eryu Guan <guaneryu@gmail.com>
84 lines
2.6 KiB
Bash
Executable File
84 lines
2.6 KiB
Bash
Executable File
#! /bin/bash
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
# Copyright (c) 2013 Fusion IO. All Rights Reserved.
|
|
#
|
|
# FS QA Test No. btrfs/016
|
|
#
|
|
# btrfs send hole punch test
|
|
#
|
|
seq=`basename $0`
|
|
seqres=$RESULT_DIR/$seq
|
|
echo "QA output created by $seq"
|
|
|
|
tmp=`mktemp -d`
|
|
tmp_dir=send_temp_$seq
|
|
|
|
status=1 # failure is the default!
|
|
|
|
_cleanup()
|
|
{
|
|
$BTRFS_UTIL_PROG subvolume delete $TEST_DIR/$tmp_dir/snap > /dev/null 2>&1
|
|
$BTRFS_UTIL_PROG subvolume delete $TEST_DIR/$tmp_dir/snap1 > /dev/null 2>&1
|
|
$BTRFS_UTIL_PROG subvolume delete $TEST_DIR/$tmp_dir/send > /dev/null 2>&1
|
|
rm -rf $TEST_DIR/$tmp_dir
|
|
rm -f $tmp.*
|
|
}
|
|
|
|
trap "_cleanup ; exit \$status" 0 1 2 3 15
|
|
|
|
# get standard environment, filters and checks
|
|
. ./common/rc
|
|
. ./common/filter
|
|
|
|
# real QA test starts here
|
|
_supported_fs btrfs
|
|
_require_test
|
|
_require_scratch
|
|
_require_fssum
|
|
_require_xfs_io_command "falloc"
|
|
|
|
_scratch_mkfs > /dev/null 2>&1
|
|
|
|
#receive needs to be able to setxattrs, including the selinux context, if we use
|
|
#the normal nfs context thing it screws up our ability to set the
|
|
#security.selinux xattrs so we need to disable this for this test
|
|
export SELINUX_MOUNT_OPTIONS=""
|
|
|
|
_scratch_mount
|
|
|
|
mkdir $TEST_DIR/$tmp_dir
|
|
$BTRFS_UTIL_PROG subvolume create $TEST_DIR/$tmp_dir/send \
|
|
> $seqres.full 2>&1 || _fail "failed subvolume create"
|
|
|
|
_ddt of=$TEST_DIR/$tmp_dir/send/foo bs=1M count=10 >> $seqres.full \
|
|
2>&1 || _fail "dd failed"
|
|
$BTRFS_UTIL_PROG subvolume snapshot -r $TEST_DIR/$tmp_dir/send \
|
|
$TEST_DIR/$tmp_dir/snap >> $seqres.full 2>&1 || _fail "failed snap"
|
|
$XFS_IO_PROG -c "fpunch 1m 1m" $TEST_DIR/$tmp_dir/send/foo
|
|
$BTRFS_UTIL_PROG subvolume snapshot -r $TEST_DIR/$tmp_dir/send \
|
|
$TEST_DIR/$tmp_dir/snap1 >> $seqres.full 2>&1 || _fail "failed snap"
|
|
|
|
$FSSUM_PROG -A -f -w $tmp/fssum.snap $TEST_DIR/$tmp_dir/snap >> $seqres.full \
|
|
2>&1 || _fail "fssum gen failed"
|
|
$FSSUM_PROG -A -f -w $tmp/fssum.snap1 $TEST_DIR/$tmp_dir/snap1 >> $seqres.full \
|
|
2>&1 || _fail "fssum gen failed"
|
|
|
|
$BTRFS_UTIL_PROG send -f $tmp/send.snap $TEST_DIR/$tmp_dir/snap >> \
|
|
$seqres.full 2>&1 || _fail "failed send"
|
|
$BTRFS_UTIL_PROG send -p $TEST_DIR/$tmp_dir/snap \
|
|
-f $tmp/send.snap1 $TEST_DIR/$tmp_dir/snap1 \
|
|
>> $seqres.full 2>&1 || _fail "failed send"
|
|
|
|
$BTRFS_UTIL_PROG receive -f $tmp/send.snap $SCRATCH_MNT >> $seqres.full 2>&1 \
|
|
|| _fail "failed recv"
|
|
$BTRFS_UTIL_PROG receive -f $tmp/send.snap1 $SCRATCH_MNT >> $seqres.full 2>&1 \
|
|
|| _fail "failed recv"
|
|
|
|
$FSSUM_PROG -r $tmp/fssum.snap $SCRATCH_MNT/snap >> $seqres.full 2>&1 \
|
|
|| _fail "fssum failed"
|
|
$FSSUM_PROG -r $tmp/fssum.snap1 $SCRATCH_MNT/snap1 >> $seqres.full 2>&1 \
|
|
|| _fail "fssum failed"
|
|
|
|
echo "Silence is golden"
|
|
status=0 ; exit
|