new file mode 100755
@@ -0,0 +1,85 @@
+#! /bin/bash
+# FS QA Test No. 350
+#
+# Use the XFS log record CRC error injection mechanism to test torn writes to
+# the log. The error injection mechanism writes an invalid CRC and shuts down
+# the filesystem. The test verifies that a subsequent remount recovers the log
+# and that the filesystem is consistent.
+#
+# Note that this test requires a DEBUG mode kernel.
+#
+#-----------------------------------------------------------------------
+# Copyright (c) 2015 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.*
+ killall -9 fsstress > /dev/null 2>&1
+ wait > /dev/null 2>&1
+}
+
+rm -f $seqres.full
+
+# get standard environment, filters and checks
+. ./common/rc
+
+# real QA test starts here
+
+# Modify as appropriate.
+_supported_fs xfs
+_supported_os Linux
+_require_xfs_sysfs $(_short_dev $SCRATCH_DEV)/log/log_badcrc_factor
+_require_scratch
+
+echo "Silence is golden."
+
+_scratch_mkfs >> $seqres.full 2>&1 || _fail "mkfs failed"
+_scratch_mount
+
+sdev=$(_short_dev $SCRATCH_DEV)
+
+for i in $(seq 1 5); do
+ # Enable error injection. Use a random bad crc factor up to 100
+ # (increase this value to run fsstress longer).
+ factor=$((RANDOM % 100))
+ echo iteration $i log_badcrc_factor: $factor >> $seqres.full 2>&1
+ echo $factor > /sys/fs/xfs/$sdev/log/log_badcrc_factor
+
+ # Run fsstress until the filesystem shuts down. It will shut down
+ # automatically when error injection triggers.
+ $FSSTRESS_PROG -d $SCRATCH_MNT -p 4 -n 999999 >> $seqres.full 2>&1
+
+ # Verify that we can remount the fs. Log recovery should handle the torn
+ # write.
+ _scratch_unmount
+ _scratch_mount || _fail "failed to mount"
+done
+
+# success, all done
+status=0
+exit
new file mode 100644
@@ -0,0 +1,2 @@
+QA output created by 350
+Silence is golden.
@@ -220,3 +220,4 @@
303 auto quick quota
304 auto quick quota
305 auto quota
+350 auto log metadata
XFS torn log write detection includes a mechanism to inject CRC errors into log records at runtime and shutdown the fs accordingly. This ensures that the CRC verification pass on the subsequent mount discovers an invalid record near the head of the log and considers it a torn write. This test runs a workload with error injection enabled and verifies that the subsequent mount is successful. The test repeats for several iterations using a random frequency factor for the error event each time. Signed-off-by: Brian Foster <bfoster@redhat.com> --- Hi all, This test accompanies the torn log write detection series here: http://oss.sgi.com/pipermail/xfs/2015-November/044945.html ... and is based on the associated test mechanism. Note that this is quick and dirty and subject to change based on review of that series. I also hadn't put too much thought into how many iterations to use, how long the test should run in general and what the range of the injection param should be. As such, this is RFC for now. Thoughts appreciated. Brian tests/xfs/350 | 85 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/xfs/350.out | 2 ++ tests/xfs/group | 1 + 3 files changed, 88 insertions(+) create mode 100755 tests/xfs/350 create mode 100644 tests/xfs/350.out