From: Dave Chinner <david@fromorbit.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Jayashree Mohan <jayashree2912@gmail.com>,
Eryu Guan <guaneryu@gmail.com>, fstests <fstests@vger.kernel.org>,
Vijaychidambaram Velayudhan Pillai <vijay@cs.utexas.edu>,
Amir Goldstein <amir73il@gmail.com>,
Filipe Manana <fdmanana@gmail.com>
Subject: Re: [PATCH] fstest: CrashMonkey tests ported to xfstest
Date: Wed, 7 Nov 2018 10:39:56 +1100 [thread overview]
Message-ID: <20181106233956.GX6311@dastard> (raw)
In-Reply-To: <20181106231536.GB8691@thunk.org>
On Tue, Nov 06, 2018 at 06:15:36PM -0500, Theodore Y. Ts'o wrote:
> On Mon, Nov 05, 2018 at 02:16:57PM -0600, Jayashree Mohan wrote:
> >
> > I believe that to _scratch_mkfs, I must first _cleanup dm_flakey. If I replace the above snippet by
> > _cleanup
> > _scratch_mkfs
> > _init_flakey
> >
> > The time taken for the test goes up by around 10 seconds (due to mkfs maybe). So I thought it was sufficient to remove the working directory.
>
> Can you try adding _check_scratch_fs after each test case? Yes, it
_check_scratch_fs now runs xfs_scrub on XFS as well as xfs_repair,
so it's actually quite expensive.
The whole point of aggregating all these tests into one fstest is to
avoid the overhead of running _check_scratch_fs after every single
test that are /extremely unlikely/ to fail on existing filesystems.
> Also, how big does the file system have to be? I wonder if we can
> speed things up if a ramdisk is used as the backing device for
> dm-flakey.
I already run fstests on pmem devices for fast iteration of the
entire test suite. The slowest part of the test suite for quick
tests is still the filesystem checking between tests. So putting
dm-flakey on a ramdisk doesn't help anything here.
I also run fstests on memory constrained VMs, where there isn't ram
to add a ramdisk for random stuff like this. Then all the dm-flakey
tests either wont run or fail due to OOM-kills.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-11-07 9:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 16:50 [PATCH] fstest: CrashMonkey tests ported to xfstest Jayashree Mohan
2018-10-30 13:05 ` Filipe Manana
2018-11-02 20:39 ` Jayashree Mohan
2018-11-04 16:27 ` Eryu Guan
2018-11-04 16:38 ` Eryu Guan
2018-11-04 20:21 ` Jayashree Mohan
2018-11-05 5:22 ` Dave Chinner
2018-11-05 20:16 ` Jayashree Mohan
2018-11-06 22:57 ` Dave Chinner
2018-11-06 23:15 ` Theodore Y. Ts'o
2018-11-06 23:39 ` Dave Chinner [this message]
[not found] ` <CA+EzBbDwdi26MCswz0iQ8hUTcGixATUXayxMOmEw5gekYvmMuw@mail.gmail.com>
[not found] ` <5be228d2.1c69fb81.3ad08.5e76.GMR@mx.google.com>
2018-11-06 23:54 ` Delivery Status Notification (Failure) Jayashree Mohan
2018-11-07 2:09 ` [PATCH] fstest: CrashMonkey tests ported to xfstest Dave Chinner
2018-11-07 4:04 ` Theodore Y. Ts'o
2018-11-08 1:41 ` Jayashree Mohan
2018-11-08 9:10 ` Dave Chinner
2018-11-08 14:46 ` Jayashree Mohan
2018-11-08 9:40 ` Dave Chinner
2018-11-08 15:35 ` Vijaychidambaram Velayudhan Pillai
2018-11-09 3:12 ` Dave Chinner
2018-11-09 16:39 ` Vijaychidambaram Velayudhan Pillai
2018-11-09 19:17 ` Theodore Y. Ts'o
2018-11-09 20:47 ` Vijaychidambaram Velayudhan Pillai
2018-11-08 16:10 ` Theodore Y. Ts'o
2018-11-07 0:24 ` Jayashree Mohan
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=20181106233956.GX6311@dastard \
--to=david@fromorbit.com \
--cc=amir73il@gmail.com \
--cc=fdmanana@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=jayashree2912@gmail.com \
--cc=tytso@mit.edu \
--cc=vijay@cs.utexas.edu \
/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.