From: Anand Jain <Anand.Jain@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: xfstest/btrfs _require_scratch_dev_pool runs btrfsck
Date: Thu, 14 Aug 2014 18:54:13 +0800 [thread overview]
Message-ID: <53EC9555.80403@oracle.com> (raw)
Here below is a simple test script. I can't understand why
_require_scratch_dev_pool should check consistency on the disk ?
-------------
#! /bin/bash
# Test case 060
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
tmp=/tmp/$$
status=1 # failure is the default!
trap "_cleanup; exit \$status" 0 1 2 3 15
_cleanup()
{
cd /
rm -f $tmp.tmp
}
# get standard environment, filters and checks
. ./common/rc
. ./common/filter
_require_scratch_dev_pool 4
status=0
exit
-------------
./check btrfs/060
FSTYP -- btrfs
PLATFORM -- Linux/x86_64 OL 3.16.0-rc6+
MKFS_OPTIONS -- /dev/sdc
MOUNT_OPTIONS -- /dev/sdc /mnt/scratch
btrfs/060 2s ... 1s
_check_btrfs_filesystem: filesystem on /dev/sdc is inconsistent (see
/usr/src/cli/xfstests/results//btrfs/060.full) <-----
Ran: btrfs/060
Passed all 1 tests
_check_btrfs_filesystem()
{
::
echo "_check_btrfs_filesystem: filesystem on $device is
inconsistent" >>$seqres.full
check
::
test -f ${RESULT_DIR}/require_scratch && _check_scratch_fs
reply other threads:[~2014-08-14 10:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53EC9555.80403@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).