From: Mark Fasheh <mark.fasheh@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Re: [CRASH]Oops in journal_wip on first mount
Date: Wed Mar 24 21:07:58 2004 [thread overview]
Message-ID: <20040325030753.GL10672@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20040324020542.GA13748@penguin.co.intel.com>
On Tue, Mar 23, 2004 at 06:05:42PM -0800, Rusty Lynch wrote:
> [root@nobody root]# mkfs -t ocfs2 -F -b 128 -g 0 -u 0 -L ocfs2 -m /oracle -p 775 /dev/sdb2
> Cleared volume header sectors
> Cleared node config sectors
> Cleared publish sectors
> Cleared vote sectors
> Cleared bitmap sectors
> Cleared data block
> Wrote volume header
> [root@nobody root]# tuneocfs -c 2 /dev/sdb2 Proceed (y/N): y
> Changes written to disk.
Whoa... just noticed this... If you make an ocfs2 file system (as opposed to
an "ocfs" file system), then you needn't run tuneocfs... in fact, tuneocfs
should fail on you... Now to see why it isn't :)
Ok, I do an mkfs.ocfs2 and then run tuneocfs -c 2 on the resulting file
system and i get:
(2314) ERROR: Version number not compatible: 2.0, Common/ocfsgenmisc.c, 811
(2314) ERROR: Device (0,3) failed verification, Linux/ocfsmount.c, 232
failed to mount
so, uhm, am I misunderstanding what that mount command is doing? :)
Anyway, this prolly doesn't explain the issue with journal_wipe.
--Mark
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next prev parent reply other threads:[~2004-03-24 21:07 UTC|newest]
Thread overview: 11+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 21:15 [Ocfs2-devel] " Ling, Xiaofeng
2004-03-23 21:19 Ling, Xiaofeng
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=20040325030753.GL10672@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.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.