[Ocfs2-devel] Re: [CRASH]Oops in journal_wip on first mount

Rusty Lynch rusty at linux.co.intel.com
Wed Mar 24 19:23:13 CST 2004


On Wed, Mar 24, 2004 at 07:07:53PM -0800, Mark Fasheh wrote:
> On Tue, Mar 23, 2004 at 06:05:42PM -0800, Rusty Lynch wrote:
> > [root at 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 at 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

I had a really old set of ocfs-tools. Just installed newer bits and now I 
don't need to run tuneocfs after doing a mkfs.ocfs2

    --rusty



More information about the Ocfs2-devel mailing list