public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: jfs-discussion@lists.sourceforge.net, xfs@oss.sgi.com
Subject: Re: [Jfs-discussion] [PATCH, RFC] jfs support for xfstests
Date: Fri, 29 Jul 2011 11:03:55 -0500	[thread overview]
Message-ID: <4E32D9EB.9020406@oracle.com> (raw)
In-Reply-To: <20110729155039.GA28306@infradead.org>

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.

Thanks,
Shaggy

> 
> 
> Index: xfstests-dev/common.rc
> ===================================================================
> --- xfstests-dev.orig/common.rc	2011-07-29 15:36:52.000000000 +0000
> +++ xfstests-dev/common.rc	2011-07-29 15:39:41.000000000 +0000
> @@ -102,6 +102,9 @@ _mkfs_opts()
>      gfs2)
>  	export MKFS_OPTIONS="$GFS2_MKFS_OPTIONS -O -p lock_nolock"
>  	;;
> +    jfs)
> +	export MKFS_OPTIONS="$JFS_MKFS_OPTIONS -q"
> +	;;
>      *)
>  	;;
>      esac
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-07-29 16:04 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 ` Dave Kleikamp [this message]
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

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=4E32D9EB.9020406@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=hch@infradead.org \
    --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