From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rusty Lynch <rusty@linux.co.intel.com>
Date: Wed Mar 24 21:21:52 2004
Subject: [Ocfs2-devel] [CRASH]Oops in journal_wip on first mount
In-Reply-To: <20040325031658.GM10672@ca-server1.us.oracle.com>
References: <200403240138.i2O1cm5n013594@penguin.co.intel.com>
	<20040324015604.GA13687@penguin.co.intel.com>
	<20040325031658.GM10672@ca-server1.us.oracle.com>
Message-ID: <20040325032135.GA5802@penguin.co.intel.com>
List-Id: <ocfs2-devel.oss.oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ocfs2-devel@oss.oracle.com

On Wed, Mar 24, 2004 at 07:16:58PM -0800, Mark Fasheh wrote:
> On Tue, Mar 23, 2004 at 05:56:04PM -0800, Rusty Lynch wrote:
> > Small update... I just pulled an older svn tree (version 798, the version
> > that the OCFS_VERSION_2_BETA_2 tag was laid down), and the older version
> > does not have the problem.
> > 
> > I can then go and load the version 807 module again, and attempt to mount
> > the volume again to see the Oops once again. So... first time mount doesn't
> > seem to matter.
> Ok, I'm not seeing this at all :(
> Can you assert on osb->journal.k_journal != NULL before the call to
> ocfs_journal_wipe... I wonder if somehow it's not being initialized
> properly.
> 	--Mark

I had something going on with my tree.  I have no idea what the problem was, but
chances are the problem resides between the keyboard and the chair.

Since checking out a new tree I haven't had a problem.

    --rusty