From: Brian Foster <bfoster@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/5] xfstests: fixes for the free inode btree
Date: Wed, 21 May 2014 07:31:34 -0400 [thread overview]
Message-ID: <20140521113134.GA56375@bfoster.bfoster> (raw)
In-Reply-To: <20140521002037.GL18954@dastard>
On Wed, May 21, 2014 at 10:20:37AM +1000, Dave Chinner wrote:
> On Mon, May 05, 2014 at 07:34:43AM -0400, Brian Foster wrote:
> > On Sat, May 03, 2014 at 09:48:31AM +1000, Dave Chinner wrote:
> > > On Fri, May 02, 2014 at 01:13:57PM -0400, Brian Foster wrote:
> > > > Hi all,
> > > >
> > > > This series is a few xfstests fixes and addons for the finobt. Patch 1
> > > > fixes xfs/030 to work correctly on finobt-enabled filesystems. Patches 2
> > > > and 3 add support for finobt-oriented tests via require functions and
> > > > repair filter updates. Patch 4 adds a new test for targeted repair of
> > > > finobt filesystems. Patch 5 adds a stress test that creates/modifies a
> > > > sparsely allocated set of inodes to effectively exercise the finobt in
> > > > conjunction with an fsstress workload.
> > > >
> > > > xfs/010 runs very quickly. xfs/013 runs for 5-10 minutes on my smallish
> > > > VM running against a single spindle, so I've been back and forth on
> > > > whether it should be part of the auto group. Thoughts, reviews, flames
> > > > appreciated...
> > >
> > > 5-10 minutes is probably right at the edge for auto, but I think
> > > that most people won't be testing this any time soon. Hence I'd
> > > include it by default in the auto group, and if people complain
> > > about the runtime when they start testing it, we can revist that
> > > choice. FWIW, I'd also include it in the metadata group so that it
> > > gets exercised when people run that group....
> > >
> >
> > Ok, sounds good. It actually runs closer to 5 minutes than 10 when I
> > simply move to a separate (still single) spindle, so it's probably not
> > that bad. IIRC, it's still probably not the longest running test I've
> > seen in auto. I believe you have an SSD test setup, so I'm curious how
> > the workload looks if you get a a chance to run it there. :)
>
> FWIW, just running xfs/013 on 2 sata drives in hw RAID1 takes 80-90s
> to run xfs/013, so this is fine. However, it runs out of disk space
> on a 4GB ramdisk, so it still might need some tweaking...
>
Noted, I'll look into it. Thanks.
Brian
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-05-21 11:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 17:13 [PATCH 0/5] xfstests: fixes for the free inode btree Brian Foster
2014-05-02 17:13 ` [PATCH 1/5] xfs/030: filter out extra repair noise for finobt enabled fs' Brian Foster
2014-05-02 17:13 ` [PATCH 2/5] xfstests: add _require_xfs_[mkfs_]finobt() checks for finobt tests Brian Foster
2014-05-02 17:14 ` [PATCH 3/5] xfstests: filter agno/ino repair output for finobt Brian Foster
2014-05-02 17:14 ` [PATCH 4/5] xfs/010: test repair for finobt corruption Brian Foster
2014-05-02 17:14 ` [PATCH 5/5] xfs/013: stress the free inode btree Brian Foster
2014-05-02 23:48 ` [PATCH 0/5] xfstests: fixes for " Dave Chinner
2014-05-05 11:34 ` Brian Foster
2014-05-21 0:20 ` Dave Chinner
2014-05-21 11:31 ` Brian Foster [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=20140521113134.GA56375@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=david@fromorbit.com \
--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).