[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: 0.0.3d-e: JFS: Unrecognised features on journal



here's a quote from Stephen:

> ext3-0.0.5d did not always initialise the features flags correctly
> when creating a new journal.  Fixed in 0.0.5e.  As long as you can
> still mount the filesystem, there's an easy upgrade path: you can
> do a clean shutdown, and on the next mount, use the lilo option "rw
> rootflags=noload,journal=<nnn>" where nnn is the inode number of the
> journal file.
> 
> In other words, it's just like creating the journal in the first
> place, except that you also have the "noload" option to prevent it
> from loading the existing journal first.

give that a shot, given a clean shutdown previous to using those options.
it worked perfectly for me.

-tcl.


On Wed, 24 Jan 2001, Brian J. Murrell wrote:

> I updated my kernel from 0.0.3d to 0.0.3e using the "d-e" patch in the
> 0.0.3e tarball.  When I try to boot the new kernel on a machine with
> an ext3 root filesystem I am getting the message:
> 
>     JFS: Unrecognised features on journal
> 
> Does this sound feasible or even somewhat expected?  Is there any
> interest in me doing some debugging of this?
> 
> Is there any way to deal with this without having to boot the new
> kernel with ext2 and recreating the journal?
> 
> b.
> 
> -- 
> Brian J. Murrell
> 
> 
> 
> _______________________________________________
> Ext3-users mailing list
> Ext3-users redhat com
> https://listman.redhat.com/mailman/listinfo/ext3-users
> 





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]