From: Rich Johnston <rjohnston@sgi.com>
To: Dave Chinner <david@fromorbit.com>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/7] xfstests: various fixes and additions for XFS
Date: Wed, 22 Jan 2014 07:26:37 -0600 [thread overview]
Message-ID: <52DFC70D.1010206@sgi.com> (raw)
In-Reply-To: <1390198957-17184-1-git-send-email-david@fromorbit.com>
On 01/20/2014 12:22 AM, Dave Chinner wrote:
> Hi folks,
>
> The following series cleans up some of the infrastructure for
> handling XFS filesystems, and fixes a few failures that have
> resulted from recent changes to mkfs defaults. There is also a new
> log recovery test that uses fsstress to generate load and log
> traffic. This was causing failures and hangs on recent kernels.
>
> Cheers,
>
> Dave.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
This series has been committed.
Thanks
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-01-22 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 6:22 [PATCH 0/7] xfstests: various fixes and additions for XFS Dave Chinner
2014-01-20 6:22 ` [PATCH 1/7] xfs: test scratch device mkfs features Dave Chinner
2014-01-20 6:22 ` [PATCH 2/7] xfs: New _require_* tests for CRC enabled filesystems Dave Chinner
2014-01-20 6:22 ` [PATCH 3/7] xfs: add fsstress/recovery test Dave Chinner
2014-01-20 6:22 ` [PATCH 4/7] xfs/073, 208: remove .full output before starting the test Dave Chinner
2014-01-20 6:22 ` [PATCH 5/7] xfs: support xfs_metadump with external logs Dave Chinner
2014-01-20 6:22 ` [PATCH 6/7] xfs/104: use fixed log size Dave Chinner
2014-01-20 6:22 ` [PATCH 7/7] generic/204: use fixed log size for XFS Dave Chinner
2014-01-22 11:52 ` [PATCH 0/7] xfstests: various fixes and additions " Christoph Hellwig
2014-01-22 13:26 ` Rich Johnston [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=52DFC70D.1010206@sgi.com \
--to=rjohnston@sgi.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).