From: Christoph Hellwig <hch@infradead.org>
To: Dave Kleikamp <dave.kleikamp@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
jfs-discussion@lists.sourceforge.net, xfs@oss.sgi.com
Subject: Re: [PATCH] jfs: flush journal completely before releasing metadata inodes
Date: Mon, 1 Aug 2011 14:32:55 -0400 [thread overview]
Message-ID: <20110801183255.GA30985@infradead.org> (raw)
In-Reply-To: <4E36F086.4070900@oracle.com>
On Mon, Aug 01, 2011 at 01:29:26PM -0500, Dave Kleikamp wrote:
> On 07/29/2011 11:03 AM, Dave Kleikamp wrote:
> > On 07/29/2011 10:50 AM, Christoph Hellwig wrote:
> >> The patch below adds basic jfs support to xfstests. Unfortunately it
> >> doesn't get very far, as test 001 already blows up with a kernel crash,
> >> as do 011 and 013 as other random picks.
> >
> > Great :-)
> >
> > Seems to be a good idea to support jfs. I'll carve out some time to
> > reproduce and debug the crashes.
>
> This fixes a race during unmount. We need to not only make sure that
> the journal is completely written, but that the metadata changes make
> it to disk before releasing ipimap and ipbmap.
Looks sensible. How far does a ./check -g auto get now? Any other
failures?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-08-01 18:33 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 [this message]
2011-08-01 20:04 ` Dave Kleikamp
2011-08-02 10:25 ` Christoph Hellwig
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=20110801183255.GA30985@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