From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: Dave Chinner <david@fromorbit.com>
Cc: guaneryu@gmail.com, fstests@vger.kernel.org
Subject: Re: [PATCH v2] common/rc: Add _require_filefrag_options() to check options for filefrag
Date: Tue, 27 Nov 2018 10:47:58 +0800 [thread overview]
Message-ID: <5BFCB05E.9050803@cn.fujitsu.com> (raw)
In-Reply-To: <20181126215007.GA19305@dastard>
On 2018/11/27 5:50, Dave Chinner wrote:
> On Fri, Nov 23, 2018 at 01:24:23PM +0800, Xiao Yang wrote:
>> In generic/519, filefrag command use FIBMAP ioctl(-B option) to print
>> output in extent format(-e option) on purpose and sync file(-s option),
>> so add _require_filefrag_options() to check if the command supports
>> all of these options.
>>
>> References:
>> 1) filefrag supports -e option by commit 2508eaa since e2fsprogs v1.42.7.
>> 2) filefrag supports -B option by commit 5d5e01d since e2fsprogs v1.41.9.
>> 3) filefrag supports -s option by commit e62847c since e2fsprogs v1.41.6.
>>
>> Signed-off-by: Xiao Yang<yangx.jy@cn.fujitsu.com>
>> ---
>> common/rc | 15 ++++++++++++++-
>> tests/generic/519 | 2 +-
>> 2 files changed, 15 insertions(+), 2 deletions(-)
>>
>> diff --git a/common/rc b/common/rc
>> index ecb1738..e5da648 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -3843,10 +3843,23 @@ _require_scratch_btime()
>> _scratch_unmount
>> }
>>
>> -_require_fibmap()
>> +_require_filefrag_options()
>> {
>> _require_command "$FILEFRAG_PROG" filefrag
>>
>> + local options=$1
>> + local file="$TEST_DIR/options_testfile"
>> +
>> + echo "XX"> $file
>> + ${FILEFRAG_PROG} -$options $file 2>&1 | grep -q "invalid option"&& \
>> + _notrun "filefrag doesn't support $options option"
>> + rm -f $file
>> +}
> Can we just get rid of filefrag and use xfs_io's fiemap commands
> instead?
Hi Dave,
According to the comment in test, we have to reproduce the bug by
specifying FIBMAP ioctl instead of FIEMAP ioctl.
It seems that we can just use FIEMAP ioctl by xfs_io's fiemap command,
so we use FIBMAP ioctl forcely by filefrag
with -B option.
Best Regards,
Xiao Yang
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2018-11-27 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:41 [PATCH] common/rc: Check more options for filefrag command Xiao Yang
2018-11-23 5:12 ` Eryu Guan
2018-11-23 5:18 ` Xiao Yang
2018-11-23 5:24 ` [PATCH v2] common/rc: Add _require_filefrag_options() to check options for filefrag Xiao Yang
2018-11-26 21:50 ` Dave Chinner
2018-11-27 2:47 ` Xiao Yang [this message]
2018-11-29 1:55 ` 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=5BFCB05E.9050803@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.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