public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, fstests@vger.kernel.org,
	gce-xfstests@googlegroups.com
Cc: Luis de Bethencourt <luisbg@osg.samsung.com>
Subject: Refreshed test appliance image kvm-xfstests and gce-xfstests
Date: Tue, 9 Aug 2016 00:28:28 -0400	[thread overview]
Message-ID: <20160809042828.GF9515@thunk.org> (raw)

There are updated rootfs.img files available at:

    https://www.kernel.org/pub/linux/kernel/people/tytso/kvm-xfstests

It includes the latest updates from the xfstests-dev upstream.  (For
ext4 developers, note that this includes a test for expanding the
i_extra_isize space that will cause non-patched kernels to hang unless
you have Jan Kara's patches to fix bugs in that code.  So you may want
to add -X ext4/022 to your gce-xfstests or kvm-xfstests command line.)
For information on how to use this images, please see:

https://github.com/tytso/xfstests-bld/blob/master/Documentation/kvm-quickstart.md

Also new in this release is support for btrfs.  Internally, I've
removed most of the ext4 dependencies so that people interested in
using kvm-xfstests and gce-xfstests for testing other file systems
will have a much easier time to add new test configs.  Feel free to
send me patches or the fs configs you would most like to see for your
file system (basically, I need the mkfs and mount options that are
most interesting).  We currently have basic support for btrfs, ext2,
tmpfs, and xfs in this release, in addition to ext4.

Finally, I have started making public GCE images so you don't have to
build your own copy of xfstests and then create your own GCE image.
This should hopefully make life much easier for people who want to try
out gce-xfstests.  For more information, please see:

https://github.com/tytso/xfstests-bld/blob/master/Documentation/gce-xfstests.md

Cheers,

						- Ted

                 reply	other threads:[~2016-08-09  4:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160809042828.GF9515@thunk.org \
    --to=tytso@mit.edu \
    --cc=fstests@vger.kernel.org \
    --cc=gce-xfstests@googlegroups.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=luisbg@osg.samsung.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