From: Rusty Lynch <rusty@linux.co.intel.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Crash in ocfs_volume_thread
Date: Wed Mar 17 17:12:15 2004 [thread overview]
Message-ID: <20040317231157.GA22672@penguin.co.intel.com> (raw)
In-Reply-To: <20040317223216.GL20057@ca-server1.us.oracle.com>
On Wed, Mar 17, 2004 at 02:32:16PM -0800, Mark Fasheh wrote:
> On Wed, Mar 17, 2004 at 01:42:12PM -0800, Villalovos, John L wrote:
> > I am trying to debug an issue where I get a crash in the
> > ocfs_volume_thread.
> >
> > Here is the scenario.
> >
> > This is all done under a 2.6.x kernel
> >
> > I have a corrupted partition (I think).
> >
> > I created this corrupted partition by:
> >
> > 1. Run mkfs.ocfs2
> > 2. Mount the partition once. This caused errors.
> > 3. Reboot the system.
> > 4. Try to mount the partition again and then it crashes in the
> > ocfs_volume_thread.
> Hmm, this particular scenario I don't believe has been considered very
> much... (trying to mount a partition that failed the whole 1st mount
> business)
I currently get around this bug by making sure my first mount of a
partition is from a 2.4 build. Maybe the fix for this is to just
go ahead and rip out the first mount logic and place it in mkfs.ocfs
like has mentioned before.
next prev parent reply other threads:[~2004-03-17 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 15:42 [Ocfs2-devel] Crash in ocfs_volume_thread Villalovos, John L
2004-03-17 16:32 ` Mark Fasheh
2004-03-17 17:12 ` Rusty Lynch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-17 17:45 Villalovos, John L
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=20040317231157.GA22672@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.