From: Eric Sandeen <sandeen@sandeen.net>
To: Josef Bacik <jbacik@fb.com>,
linux-btrfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: fix flink test
Date: Wed, 07 May 2014 23:16:27 -0500 [thread overview]
Message-ID: <536B051B.20400@sandeen.net> (raw)
In-Reply-To: <1399496087-20431-1-git-send-email-jbacik@fb.com>
On 5/7/14, 3:54 PM, Josef Bacik wrote:
> I don't have flink support in my xfsprogs, but it doesn't fail with "command not
> found" or whatever, it fails because I don't have the -T option. So fix
> _require_xfs_io_command to check for an invalid option and not run. This way I
> get notrun instead of a failure. Thanks,
This actually doesn't work for me on an old kernel, if that matters; it
fails with:
/mnt/test: Is a directory
and nothing catches that. Old xfsprogs tries to open the file
in question RDWR even before it gets to the -T option (which
would fail, I guess), and you can't do that for directories.
So I suppose we could explicitly test for that when checking
flink:
[ $command = "flink" ] && echo $testio | grep -q "Is a directory" && \
_notrun "xfs_io flink support is missing"
or alternately, first just run xfs_io w/ the command but no file;
today, at least, that works:
[root@bp-05 xfstests]# xfs_io -c flink
command "flink" not found
[root@bp-05 xfstests]# xfs_io -c pread
[root@bp-05 xfstests]#
so could do this before the case statement:
$XFS_IO_PROG -c $command 2>&1 | grep -q "not found" && \
_notrun "xfs_io $command support is missing"
but that might be subject to future changes in xfs_io command
parsing...
-Eric
> Signed-off-by: Josef Bacik <jbacik@fb.com>
> ---
> common/rc | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/common/rc b/common/rc
> index 5c13db5..4fa7e63 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -1258,6 +1258,8 @@ _require_xfs_io_command()
> _notrun "xfs_io $command support is missing"
> echo $testio | grep -q "Operation not supported" && \
> _notrun "xfs_io $command failed (old kernel/wrong fs?)"
> + echo $testio | grep -q "invalid option" && \
> + _notrun "xfs_io $command support is missing"
> }
>
> # Check that a fs has enough free space (in 1024b blocks)
> -- 1.8.3.1 _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
>
prev parent reply other threads:[~2014-05-08 4:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 20:54 [PATCH] xfstests: fix flink test Josef Bacik
2014-05-07 22:44 ` Dave Chinner
2014-05-08 4:16 ` Eric Sandeen [this message]
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=536B051B.20400@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).