From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: fstests@vger.kernel.org
Cc: Chandan Rajendra <chandan@linux.vnet.ibm.com>,
guaneryu@gmail.com, darrick.wong@oracle.com, zlang@redhat.com,
linux-xfs@vger.kernel.org
Subject: [PATCH V4 14/20] Filter fiemap output by FS block size
Date: Wed, 19 Sep 2018 17:30:47 +0530 [thread overview]
Message-ID: <20180919120053.7339-15-chandan@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180919120053.7339-1-chandan@linux.vnet.ibm.com>
When testing FS instances of block size other than 4k, the output of
fiemap command will not match those in *.out files. This commit adds
an optional "block size" argument to _filter_fiemap() which prints
fiemap output in units of block size.
Signed-off-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
---
common/punch | 19 ++++++++++++++-----
1 file changed, 14 insertions(+), 5 deletions(-)
diff --git a/common/punch b/common/punch
index 8088b01..0fc7729 100644
--- a/common/punch
+++ b/common/punch
@@ -165,7 +165,11 @@ _test_punch() {
_coalesce_extents()
{
- awk -F: '
+ block_size=$1
+
+ [[ -z $block_size ]] && block_size=512
+
+ awk -v block_size="$block_size" -F: '
{
range = $2;
type = $3;
@@ -176,19 +180,24 @@ _coalesce_extents()
if (type != prev_type) {
if (prev_type != "")
- printf("%u]:%s\n", low - 1, prev_type);
- printf("%u: [%u..", out_count++, low);
+ printf("%u]:%s\n", (low * 512 / block_size) - 1,
+ prev_type);
+ printf("%u: [%u..", out_count++,
+ (low * 512) / block_size);
prev_type = type;
}
}
END {
if (prev_type != "")
- printf("%u]:%s\n", high, prev_type);
+ printf("%u]:%s\n", ((high + 1) * 512 / block_size) - 1,
+ prev_type);
}'
}
_filter_fiemap()
{
+ block_size=$1
+
$AWK_PROG '
$3 ~ /hole/ {
print $1, $2, $3;
@@ -201,7 +210,7 @@ _filter_fiemap()
$5 ~ /0x[[:xdigit:]]+/ {
print $1, $2, "data";
}' |
- _coalesce_extents
+ _coalesce_extents $block_size
}
_filter_fiemap_flags()
--
2.9.5
next prev parent reply other threads:[~2018-09-19 17:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 12:00 [PATCH V4 00/20] Fix tests to work on non-4k block sized fs instances Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 01/20] Fix xfs/009 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 02/20] xfs/050: Fix "Push past soft inode limit" case Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 03/20] Fix xfs/050 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 04/20] Fix xfs/074 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 05/20] Fix xfs/127 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 06/20] Fix xfs/139 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 07/20] Fix xfs/140 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 08/20] Fix xfs/190 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 09/20] xfs/299: Fix "Push past soft inode limit" case Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 10/20] Fix xfs/299 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 11/20] xfs/325: Inject free_extent error after CoW operation Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 12/20] Fix generic/102 to work with 64k block size Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 13/20] Fix generic/172 " Chandan Rajendra
2018-09-19 12:00 ` Chandan Rajendra [this message]
2018-09-19 12:00 ` [PATCH V4 15/20] Fix generic/177 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 16/20] Fix generic/230 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 17/20] Fix generic/235 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 18/20] Fix generic/459 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 19/20] Fix generic/018 " Chandan Rajendra
2018-09-19 12:00 ` [PATCH V4 20/20] Fix generic/108 " Chandan Rajendra
2018-09-20 9:33 ` [PATCH V4 00/20] Fix tests to work on non-4k block sized fs instances Zorro Lang
2018-09-22 16:24 ` Eryu Guan
2018-09-24 10:04 ` Chandan Rajendra
2018-09-24 14:19 ` Eryu Guan
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=20180919120053.7339-15-chandan@linux.vnet.ibm.com \
--to=chandan@linux.vnet.ibm.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@redhat.com \
/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