Files
apfstests/tests/generic/050
T
Darrick J. Wong b0415daaa9 generic/050: fix ro blockdev mount of xfs with quota
In XFS, mounting with quota always require a writable device.  If
the block device is read only, the mount fails, which fails this
test.  Since this is expected, work around this by simulating the
golden output when we expect a mount failure.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
2018-12-22 22:19:03 +08:00

144 lines
3.7 KiB
Bash
Executable File

#! /bin/bash
# SPDX-License-Identifier: GPL-2.0
# Copyright (c) 2009 Christoph Hellwig.
#
# FS QA Test No. 050
#
# Check out various mount/remount/unmount scenarious on a read-only blockdev.
#
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
here=`pwd`
tmp=/tmp/$$
status=1 # failure is the default!
_cleanup()
{
cd /
blockdev --setrw $SCRATCH_DEV
}
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 generic
_supported_os Linux
_require_scratch_nocheck
_require_scratch_shutdown
_require_local_device $SCRATCH_DEV
_require_norecovery
_scratch_mkfs >/dev/null 2>&1
filter_ro_mount() {
local arg=""
if [ -n "$expect_mount_failure" ]; then
arg="s|mount: $SCRATCH_MNT: permission denied|mount: device write-protected, mounting read-only|g"
fi
sed -e "$arg" | _filter_ro_mount
}
# Mounting with quota on XFS requires a writable fs, which means
# we expect to fail the ro blockdev test with with EPERM.
expect_mount_failure=
if [ "$FSTYP" = "xfs" ] && echo "$MOUNT_OPTIONS" | grep -q quota ; then
expect_mount_failure=1
fi
#
# Mark the device read-only
#
echo "setting device read-only"
blockdev --setro $SCRATCH_DEV
#
# Mount it, and make sure we can't write to it, and we can unmount it again
#
echo "mounting read-only block device:"
_try_scratch_mount 2>&1 | filter_ro_mount
if [ "${PIPESTATUS[0]}" -eq 0 ]; then
echo "touching file on read-only filesystem (should fail)"
touch $SCRATCH_MNT/foo 2>&1 | _filter_scratch
#
# Apparently this used to be broken at some point:
# http://oss.sgi.com/bugzilla/show_bug.cgi?id=807
#
echo "unmounting read-only filesystem"
_scratch_unmount 2>&1 | _filter_scratch
elif [ -n "${expect_mount_failure}" ]; then
# Mount failed, so simulate EROFS instead of scribbling on root fs
echo "touching file on read-only filesystem (should fail)"
echo "touch: cannot touch 'SCRATCH_MNT/foo': Read-only file system"
echo "unmounting read-only filesystem"
else
echo "Mount failed, though it wasn't supposed to!"
fi
echo "setting device read-write"
blockdev --setrw $SCRATCH_DEV
echo "mounting read-write block device:"
_try_scratch_mount 2>&1 | _filter_scratch
echo "touch files"
touch $SCRATCH_MNT/{0,1,2,3,4,5,6,7,8,9}{0,1,2,3,4,5,6,7,8,9}
echo "going down:"
src/godown -f $SCRATCH_MNT
echo "unmounting shutdown filesystem:"
_scratch_unmount 2>&1 | _filter_scratch
echo "setting device read-only"
blockdev --setro $SCRATCH_DEV
#
# Mounting a filesystem that requires log-recovery fails unless
# -o norecovery is used.
#
echo "mounting filesystem that needs recovery on a read-only device:"
_try_scratch_mount 2>&1 | _filter_ro_mount
echo "unmounting read-only filesystem"
_scratch_unmount 2>&1 | _filter_scratch | _filter_ending_dot
#
# This is the way out if the underlying device really is read-only.
# Doesn't mean it's a good idea in practice, more a last resort
# data recovery hack.
#
echo "mounting filesystem with -o norecovery on a read-only device:"
_try_scratch_mount -o norecovery 2>&1 | filter_ro_mount
if [ "${PIPESTATUS[0]}" -eq 0 ]; then
echo "unmounting read-only filesystem"
_scratch_unmount 2>&1 | _filter_scratch
elif [ -n "${expect_mount_failure}" ]; then
# Mount failed, simulate correct output
echo "unmounting read-only filesystem"
else
echo "Mount failed, though it wasn't supposed to!"
fi
echo "setting device read-write"
blockdev --setrw $SCRATCH_DEV
#
# But log recovery is performed when mount with -o ro as long as
# the underlying device is not write protected.
#
echo "mounting filesystem that needs recovery with -o ro:"
_try_scratch_mount -o ro 2>&1 | _filter_scratch
# success, all done
echo "*** done"
rm -f $seqres.full
status=0