How to convert from ext3 back to ext2 

Ok, what I did was booted with 'linux single' then ran 'umount /' and 'umount /boot'. Then I ran 'tune2fs -O ^has_journal /dev/hda[x]' on both drives and changed /etc/fstab to mount as ext2.

After that the system wouldn't boot complaining about a missing journal. What am I doing wrong? I have to use the CD to rescue and go back a recreate the journal.

How can I get rid of ext3 permanently and have the system boot up to ext2?

Warren Bell

How to convert from ext3 back to ext2 

> > How can I get rid of ext3 permanently and have the system boot up to
> > ext2?
>
> Edit /etc/fstab, that's all (and you can delete the journal file if
> you want to)

I did that and the EXT3 stuff at boot was still showing up. And when I deleted the journal file the system wouldn't boot.

How to convert from ext3 back to ext2 

I read that the only real advantage of ext3 is skipping the fsck at startup. But when my system locked and I rebooted it gave me the option to do a system check. I choose yes and it's the same speed doing the fsck as ext2 was.

Now I think I have ext3 disabled. I had to reinstall the kernel wile running in ext2, then edit lilo.conf and remove the initrd line, then go into single mode and remove the journal with tune2fs -O ^has_journal /dev/…

But there's still the choice to skip fsck at boot, the one where it counts down from 5 seconds. Is this part of ext3 or is redhat just giving a choice now to fsck or not?

Also, after getting everything back to ext2 I shut the computer off in X just to test the fsck out. When I boot and X first starts I still get a flash on the screen of the desktop in the state it was when I powered off with no shutdown. I noticed it doing this when I first installed 7.2 with ext3 and thought it might be somthing to do with the journal saving the last state of the system. Since I'm still seeing this, it ext3 still active on the system?

How to convert from ext3 back to ext2 

> But there's still the choice to skip fsck at boot, the one where it
> counts down from 5 seconds.  Is this part of ext3 or is redhat just
> giving a choice now to fsck or not?

I got everything working except that there's still the chioce at boot to skip the fsck or choose yes. But now that I've removed ext3, if I choose yes to fsck it does it. If I let the time run out to skip it it does it anyway. Does anyone know how to remove this prompt to fsck? Without ext3 it doesn't do any good exept slow the boot time.

Warren Bell