Ext3 users - Jan 2002 - root fs upgraded to ext3 on rh 6.2 based machine problem when not cleanly unmounted

Hello,

I search through but I didn't find a clear answer about it.
I have a rh 6.2 based box where I made many steps of upgrades.

Some of them, not being available the binary rpm glibc 2.1 based, I 
obtained using src.rpm from rh 7.2 and then runnig

#rpm --rebuild package.src.rpm

and then installing the generated binary: great sw rpm!!!
My rpm version is 4.0.2-6x for both rpm, rpm-devel, rpm-build.

I upgraded my filesystems to ext3 using tune2fs.

Now I'm using kernel 2.4.17 with ext2 in core and ext3 as a module, so I 
have the two jbd.o and ext3.o files under /lib/modules tree.

If I power off cleanly my system I have no problem rebooting and the 
filesystem type of them is ext3 (I put ext3 for root and auto for the 
others in fstab).

If I power off uncleanly the machine, root has to make fsck (in the long 
ext2 way and complaining also), while for the other file systems the 
journal is applied and in few seconds they are ok and after booting they 
are all ext3.

What is the problem with root filesystem?


I created initrd image and I have also jbd.o and ext3.o in it, in fact
at boot time I can see root booted with kjournal  etc.


It seems to me that the problem can be with the different way rc.sysinit 
is written from rh 6.2 to 7.2, about file system checking.

Is this correct? May be sufficient to adapt this file to adhere to 7.2 
schema? Or not?

I have read in some places something like this:

WARNING : If u are converting your existing ext2 root file system to
           ext3 than compile ext3 support in the kernel since u 	
  	  will need it on startup :-)

(eg in http://www.symonds.net/~rajesh/howto/ext3/index.html)


Is it right?

Some of my packages versions:

e2fsprogs-1.25-1
mkinitrd-3.2.6-1
modutils-2.4.6-4
mount-2.11g-5
filesystem-2.1.6-2
setup-2.5.7-1



Thanks in advance.
Bye,
Gianluca Cecchi

Hello,

I search through but I didn't find a clear answer about it.
I have a rh 6.2 based box where I made many steps of upgrades.

Some of them, not being available the binary rpm glibc 2.1 based, I 
obtained using src.rpm from rh 7.2 and then runnig

#rpm --rebuild package.src.rpm

and then installing the generated binary: great sw rpm!!!
My rpm version is 4.0.2-6x for both rpm, rpm-devel, rpm-build.

I upgraded my filesystems to ext3 using tune2fs.

Now I'm using kernel 2.4.17 with ext2 in core and ext3 as a module, so I 
have the two jbd.o and ext3.o files under /lib/modules tree.

If I power off cleanly my system I have no problem rebooting and the 
filesystem type of them is ext3 (I put ext3 for root and auto for the 
others in fstab).

If I power off uncleanly the machine, root has to make fsck (in the long 
ext2 way and complaining also), while for the other file systems the 
journal is applied and in few seconds they are ok and after booting they 
are all ext3.

What is the problem with root filesystem?


I created initrd image and I have also jbd.o and ext3.o in it, in fact
at boot time I can see root booted with kjournal  etc.


It seems to me that the problem can be with the different way rc.sysinit 
is written from rh 6.2 to 7.2, about file system checking.

Is this correct? May be sufficient to adapt this file to adhere to 7.2 
schema? Or not?

I have read in some places something like this:

WARNING : If u are converting your existing ext2 root file system to
           ext3 than compile ext3 support in the kernel since u
        will need it on startup [:-)]

(eg in http://www.symonds.net/~rajesh/howto/ext3/index.html)


Is it right?

Some of my packages versions:

e2fsprogs-1.25-1
mkinitrd-3.2.6-1
modutils-2.4.6-4
mount-2.11g-5
filesystem-2.1.6-2
setup-2.5.7-1



Thanks in advance.
Bye,
Gianluca Cecchi

On Thu, Jan 03, 2002 at 03:20:03PM +0100, Gianluca Cecchi
wrote:
> Now I'm using kernel 2.4.17 with ext2 in core and ext3 as a module, so
I
> have the two jbd.o and ext3.o files under /lib/modules tree.
> 
> If I power off cleanly my system I have no problem rebooting and the 
> filesystem type of them is ext3 (I put ext3 for root and auto for the 
> others in fstab).
> 
> If I power off uncleanly the machine, root has to make fsck (in the long 
> ext2 way and complaining also), while for the other file systems the 
> journal is applied and in few seconds they are ok and after booting they 
> are all ext3.
> 
> What is the problem with root filesystem?
The problem is that it's tricky to use ext3 as a module, and wanting
to mount the root filesystem as ext3.  In order to do this, you have
to arrange your initrd image so that it loads the ext3 module before
it mounts the root filesystem.  Otherwise, the root filesystem gets
mounted as ext2, and so you don't get any of the benefits of using the
ext3 filesystem.  Remember, the filesystem is backwards compatible, so
just because you've added an ext3 journal, the filesystem can still be
mounted using ext2 --- and if you're using a kernel with ext2 built
in, and ext3 as a module (but not loaded), it will be mounted using
ext2.

The easist thing to do is to build a kernel that has ext3 compiled in.
Alternatively, you can muck with the initrd image so that the ext3
module is loaded before the (real) root filesystem is mounted.

						- Ted