From: Christoph Hellwig <hch@infradead.org>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: jfs-discussion@lists.sourceforge.net, xfs@oss.sgi.com
Subject: Re: [PATCH] jfs: flush journal completely before releasing metadata inodes
Date: Tue, 2 Aug 2011 06:25:16 -0400 [thread overview]
Message-ID: <20110802102516.GA24575@infradead.org> (raw)
In-Reply-To: <4E3706D0.1000304@oracle.com>
On Mon, Aug 01, 2011 at 03:04:32PM -0500, Dave Kleikamp wrote:
> It runs through them all. A lot of tests get skipped claiming not to be
> supported on jfs. A failure because jfs doesn't support fallocate and
> hole-punch, but no crashes.
Looks like the fallocate feature tests are broken, I'll look into fixing
it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-08-02 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 15:50 [PATCH, RFC] jfs support for xfstests Christoph Hellwig
2011-07-29 16:03 ` [Jfs-discussion] " Dave Kleikamp
2011-08-01 18:29 ` [PATCH] jfs: flush journal completely before releasing metadata inodes Dave Kleikamp
2011-08-01 18:32 ` Christoph Hellwig
2011-08-01 20:04 ` Dave Kleikamp
2011-08-02 10:25 ` Christoph Hellwig [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=20110802102516.GA24575@infradead.org \
--to=hch@infradead.org \
--cc=dave.kleikamp@oracle.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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