From: Wang Shilong <wangshilong1991@gmail.com>
To: fstests@vger.kernel.org
Cc: david@fromorbit.com, linux-btrfs@vger.kernel.org
Subject: [PATCH 1/2] xfstests,btrfs/010: use _extent_count() helper
Date: Wed, 8 Oct 2014 06:35:21 -0400 [thread overview]
Message-ID: <1412764522-15754-1-git-send-email-wangshilong1991@gmail.com> (raw)
cleanup to swith _extent_count(), this way we remove a
dependence on filefrag.
Signed-off-by: Wang Shilong <wangshilong1991@gmail.com>
---
tests/btrfs/010 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
mode change 100755 => 100644 tests/btrfs/010
diff --git a/tests/btrfs/010 b/tests/btrfs/010
old mode 100755
new mode 100644
index 371f1b8..6cfc561
--- a/tests/btrfs/010
+++ b/tests/btrfs/010
@@ -40,6 +40,7 @@ _cleanup()
# get standard environment, filters and checks
. ./common/rc
. ./common/filter
+. ./common/defrag
# real QA test starts here
@@ -47,7 +48,6 @@ _cleanup()
_supported_fs btrfs
_supported_os Linux
_require_scratch
-_require_command "/usr/sbin/filefrag"
rm -f $seqres.full
@@ -71,9 +71,9 @@ done
$BTRFS_UTIL_PROG filesystem defrag $subvol/foobar && sync
-num_extent_orig=`filefrag $subvol/foobar | awk -F ' ' '{print $2}'`
-num_extent_snap1=`filefrag $SCRATCH_MNT/snap-1/foobar | awk -F ' ' '{print $2}'`
-num_extent_snap2=`filefrag $SCRATCH_MNT/snap-2/foobar | awk -F ' ' '{print $2}'`
+num_extent_orig=`_extent_count $subvol/foobar`
+num_extent_snap1=`_extent_count $SCRATCH_MNT/snap-1/foobar`
+num_extent_snap2=`_extent_count $SCRATCH_MNT/snap-2/foobar`
echo "$num_extent_orig $num_extent_snap1 $num_extent_snap2" >> $seqres.full
--
1.8.3.1
next reply other threads:[~2014-10-08 2:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 10:35 Wang Shilong [this message]
2014-10-08 10:35 ` [PATCH 2/2] xfstests,btrfs/004: use FILEFRAG_PROG macro Wang Shilong
2014-10-08 4:20 ` Dave Chinner
[not found] ` <773629AA-9F58-4A1A-A5D0-6CC0B5121233@gmail.com>
2014-10-08 5:31 ` Wang Shilong
2014-10-08 5:54 ` Dave Chinner
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=1412764522-15754-1-git-send-email-wangshilong1991@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.