|
|
| File: [Development] / xfs-cmds / xfstests / 082 (download)
Revision 1.9, Fri Jun 29 16:06:04 2007 UTC (10 years, 3 months ago) by ddiss.longdrop.melbourne.sgi.com
For XFSQA test 018 081 082 095 the test specifies test wide mkfs options using MKFS_OPTIONS env var.
Further mkfs options are then appended by _mkfs_log at mkfs time with _scratch_mkfs_xfs.
Currently there are a few ways mkfs options are specified in XFSQA:
1) suite wide MKFS_OPTIONS are specified before tests are run
e.g.
vimes:/home/fsgqa/kali/xfsqa/xfstests # export MKFS_OPTIONS="-l size=100m"
2) test wide MKFS_OPTIONS are specified during a particular test
e.g. 119
export MKFS_OPTIONS="-l version=2,size=1200b,su=64k"
3) mkfs options are appended by a test at mkfs time
e.g. 083
_scratch_mkfs_xfs -dsize=$fsz,agcount=$ags >>$seq.full
(4) Another form of appending is just appending to MKFS_OPTIONS directly
e.g. 114:export MKFS_OPTIONS="$MKFS_OPTIONS -i parent=1"
115:export MKFS_OPTIONS="$MKFS_OPTIONS -i paths=1"
e.g. Methods (2) *and* (3) for specifiying mkfs options are used in these tests.
This causes problems, because the mkfs options fallback code assumes the
_mkfs_log _scratch_mkfs_xfs appended options are the only test specified options.
This change causes tests using _mkfs_log to only use option (2).
~
~
Merge of master-melb:xfs-cmds:29031a by kenmcd.
|
#! /bin/sh
# FS QA Test No. 082
#
# Test out the v2 stripe logs with logprint
#
#-----------------------------------------------------------------------
# Copyright (c) 2000-2003 Silicon Graphics, Inc. All Rights Reserved.
#-----------------------------------------------------------------------
#
# creator
owner=tes@melbourne.sgi.com
seq=`basename $0`
echo "QA output created by $seq"
here=`pwd`
tmp=/tmp/$$
status=1 # failure is the default!
# get standard environment, filters and checks
. ./common.rc
. ./common.filter
. ./common.log
_cleanup()
{
cd /
_cleanup_logfiles
rm -f $tmp.*
umount $SCRATCH_MNT 2>/dev/null
}
trap "_cleanup; exit \$status" 0 1 2 3 15
# real QA test starts here
_supported_fs xfs
_supported_os IRIX Linux
# prelim
rm -f $seq.full $tmp.*
_require_scratch
_require_v2log
# link correct .out file
_link_out_file $seq.op
echo "*** init FS"
umount $SCRATCH_DEV >/dev/null 2>&1
cat >$tmp.seq.params <<EOF
# mkfs-opt mount-opt start-blk
version=2 logbsize=32k 2
version=2,su=4096 logbsize=32k 8
version=2,su=32768 logbsize=32k 64
#
# expect following line to fail
#
version=2,su=36864 logbsize=32k 72
#
# following is not a power of 2 BBs
#
version=2,su=5120 logbsize=32k 10
EOF
# Do the work for various log params which
# should not effect the data content of the log
# Try with and without sync'ing - sync'ing will mean that
# the log will be written out unfilled and thus the log
# stripe can have an effect.
#
for s in sync nosync ; do
cat $tmp.seq.params \
| while read mkfs mnt start restofline
do
if [ "$mkfs" = "#" ]; then
continue
fi
if [ "$HOSTOS" = "IRIX" ]; then
# don't have umount rec at start on IRIX
# so we won't have to skip over it and get to
# another stripe boundary
start=0
fi
echo "--- mkfs=$mkfs, mnt=$mnt, sync=$s ---"
export MOUNT_OPTIONS="-o $mnt"
if ! _mkfs_log "-l $mkfs"; then
continue
fi
if [ $s = "sync" ]; then
_create_log_sync
else
_create_log
fi
if [ $? -ne 0 ]; then
continue
fi
_check_log
sync_suffix=".$s"
if [ $s = "sync" ]; then
# if sync then we have chance of DATA FORK EXTENTS items
# not hanging around very long due to inode syncing to disk
# (see comment in xfs_iflush_int())
# and this is to hard to reconcile in the op output
:
else
_print_operation
_cmp_op_output $seq.op $filtered
fi
_print_transaction_inode $start
_cmp_output $seq.trans_inode $filtered
_print_transaction_buf $start
_cmp_output $seq.trans_buf $filtered
done
done
status=0
exit