All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Lynch <rusty@linux.co.intel.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [CRASH]Oops in journal_wip on first mount
Date: Wed Mar 24 21:21:52 2004	[thread overview]
Message-ID: <20040325032135.GA5802@penguin.co.intel.com> (raw)
In-Reply-To: <20040325031658.GM10672@ca-server1.us.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

      reply	other threads:[~2004-03-24 21:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 19:39 [Ocfs2-devel] [CRASH]Oops in journal_wip on first mount Rusty Lynch
2004-03-23 19:55 ` [Ocfs2-devel] " Mark Fasheh
2004-03-23 20:05   ` Rusty Lynch
2004-03-23 21:08     ` Rusty Lynch
2004-03-24 21:07     ` Mark Fasheh
2004-03-24 21:23       ` Rusty Lynch
2004-03-23 19:56 ` [Ocfs2-devel] " Rusty Lynch
2004-03-24 21:17   ` Mark Fasheh
2004-03-24 21:21     ` Rusty Lynch [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=20040325032135.GA5802@penguin.co.intel.com \
    --to=rusty@linux.co.intel.com \
    --cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.