From: Eric Sandeen <sandeen@sandeen.net>
To: tytso@mit.edu
Cc: Christoph Hellwig <hch@infradead.org>,
ext4 development <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>, Giel de Nijs <giel@vectorwise.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 12:31:26 -0600 [thread overview]
Message-ID: <4B647AFE.5000507@sandeen.net> (raw)
In-Reply-To: <20100130172502.GA788@thunk.org>
tytso@mit.edu wrote:
> On Sat, Jan 30, 2010 at 10:15:09AM -0600, Eric Sandeen wrote:
>>> me on a 32-bit machine. The patch below fixes it up, but it seems like
>>> we should rather add a variant of that code as aio_read/write commands
>>> to xfs_io instead of adding a new test program.
>> ok, that's probably better - again, though, it takes at least a release
>> cycle before most folks can test it. But I guess that's not the end of
>> the world.
>
> Stupid question --- who uses xfs_io besides xfstests? Any chance we
> could consider dropping in some version of xfs_io into xfstests, or
> actually moving it into xfstests from xfsprogs if xfstests is the
> exclusive user of that program? I've been trying to get more people
> to use xfstests, since it would be good if more companies and more
> projects were using it --- and one of the things that makes it hard is
> all of the dependencies that it has. If there was some way we could
> gradually make xfstests more self-contained, it would certainly be
> nice.
>
> - Ted
These are the deps that I know xfstests has, to build and to run:
BuildRequires: autoconf, libtool, xfsprogs-devel, e2fsprogs-devel
BuildRequires: libacl-devel, libattr-devel, libaio-devel
Requires: bash, xfsprogs, xfsdump, perl, acl, attr, bind-utils
Requires: bc, indent, quota
which isn't so bad...
(and tests are just skipped if xfsdump isn't there)
I'm not sure an xfsprogs dependency is so onerous; plenty has depended
on e2fsprogs through the years and we've lived with that ;) But
the lag time for xfsprogs to use released xfs_io functionality is a
bit of a bummer.
But I guess I don't have a great answer for who else uses xfs_io:
xfs_io(8) xfs_io(8)
NAME
xfs_io - debug the I/O path of an XFS filesystem
SYNOPSIS
xfs_io [ -adFfmrRstx ] [ -c cmd ] ... [ -p prog ] file
DESCRIPTION
xfs_io is a debugging tool like xfs_db(8), but is aimed
at examining the regular file I/O paths rather than the
raw XFS volume itself.
I guess it's not really advertised as a generic tool, and it's
in the sbin path...
I guess I could live with it either way - I suppose my main concern
is that xfstests is a mess to package for a distro, and I really like
easy access to xfs_io for my own use outside of xfstests.
-Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@sandeen.net>
To: tytso@mit.edu
Cc: Christoph Hellwig <hch@infradead.org>,
ext4 development <linux-ext4@vger.kernel.org>,
Giel de Nijs <giel@vectorwise.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests 224: test aio hole-fill at 4g
Date: Sat, 30 Jan 2010 12:31:26 -0600 [thread overview]
Message-ID: <4B647AFE.5000507@sandeen.net> (raw)
In-Reply-To: <20100130172502.GA788@thunk.org>
tytso@mit.edu wrote:
> On Sat, Jan 30, 2010 at 10:15:09AM -0600, Eric Sandeen wrote:
>>> me on a 32-bit machine. The patch below fixes it up, but it seems like
>>> we should rather add a variant of that code as aio_read/write commands
>>> to xfs_io instead of adding a new test program.
>> ok, that's probably better - again, though, it takes at least a release
>> cycle before most folks can test it. But I guess that's not the end of
>> the world.
>
> Stupid question --- who uses xfs_io besides xfstests? Any chance we
> could consider dropping in some version of xfs_io into xfstests, or
> actually moving it into xfstests from xfsprogs if xfstests is the
> exclusive user of that program? I've been trying to get more people
> to use xfstests, since it would be good if more companies and more
> projects were using it --- and one of the things that makes it hard is
> all of the dependencies that it has. If there was some way we could
> gradually make xfstests more self-contained, it would certainly be
> nice.
>
> - Ted
These are the deps that I know xfstests has, to build and to run:
BuildRequires: autoconf, libtool, xfsprogs-devel, e2fsprogs-devel
BuildRequires: libacl-devel, libattr-devel, libaio-devel
Requires: bash, xfsprogs, xfsdump, perl, acl, attr, bind-utils
Requires: bc, indent, quota
which isn't so bad...
(and tests are just skipped if xfsdump isn't there)
I'm not sure an xfsprogs dependency is so onerous; plenty has depended
on e2fsprogs through the years and we've lived with that ;) But
the lag time for xfsprogs to use released xfs_io functionality is a
bit of a bummer.
But I guess I don't have a great answer for who else uses xfs_io:
xfs_io(8) xfs_io(8)
NAME
xfs_io - debug the I/O path of an XFS filesystem
SYNOPSIS
xfs_io [ -adFfmrRstx ] [ -c cmd ] ... [ -p prog ] file
DESCRIPTION
xfs_io is a debugging tool like xfs_db(8), but is aimed
at examining the regular file I/O paths rather than the
raw XFS volume itself.
I guess it's not really advertised as a generic tool, and it's
in the sbin path...
I guess I could live with it either way - I suppose my main concern
is that xfstests is a mess to package for a distro, and I really like
easy access to xfs_io for my own use outside of xfstests.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-30 18:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 20:05 [PATCH] xfstests 224: test aio hole-fill at 4g Eric Sandeen
2010-01-29 20:05 ` Eric Sandeen
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 10:55 ` Christoph Hellwig
2010-01-30 16:15 ` Eric Sandeen
2010-01-30 16:15 ` Eric Sandeen
2010-01-30 17:25 ` tytso
2010-01-30 17:25 ` tytso
2010-01-30 18:31 ` Eric Sandeen [this message]
2010-01-30 18:31 ` Eric Sandeen
2010-01-30 19:11 ` Christoph Hellwig
2010-01-30 19:11 ` Christoph Hellwig
2010-01-30 19:46 ` Eric Sandeen
2010-01-30 19:46 ` Eric Sandeen
2012-10-26 17:18 ` Rich Johnston
2012-10-26 17:52 ` Eric Sandeen
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=4B647AFE.5000507@sandeen.net \
--to=sandeen@sandeen.net \
--cc=giel@vectorwise.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--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 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.