I recently upgraded a redhat system from 7.1 to 7.2 and unfortunately must have missed the opportunity to convert from ext2 to ext3 during the upgrade.
Later I happened to notice that it still was using ext2 so went through the steps to convert to ext3 that I found on the internet. There seemded to be some disagreement whether the root file system could be converted while mounted or whether you needed to boot from the 7.2 system cd and then convert.
In any case, I originally ran the following command while root was mounted.
For the root file system
/sbin/tune2fs -j /dev/ida/c0d0p8
/sbin/tune2fs -c 0 -i 0 /dev/cida/c0d0p8
Also, I changed the /etc/fstab to mount an ext3 file system.
When the system boots it will only mount / as an ext2 file system, but it does mount all the others as ext3.
The /var/log/dmesg has the following snippet.
VFS: Mounted root (ext2 filesystem).
SCSI subsystem driver Revision: 1.00
Compaq SMART2 Driver (v 2.4.25)
cpqarray: Device 0x10 has been found at bus 0 dev 1 func 0
cpqarray: Finding drives on ida0 (Integrated Array)
cpqarray ida/c0d0: blksz=512 nr_blks=35553120
cpqarray: Starting firmware's background processing
blk: queue c036cca0, I/O limit 4095Mb (mask 0xffffffff)
Partition check:
ida/c0d0: p1 p2 < p5 p6 p7 p8 p9 p10 >
EXT2-fs warning (device ida0(72,8)): ext2_read_super: mounting ext3 filesystem as ext2
Freeing unused kernel memory: 120k freed Adding Swap: 526296k swap-space (priority -1) Journalled Block Device driver loaded kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,1), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,9), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,6), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,7), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ida0(72,5), internal journal EXT3-fs: mounted filesystem with ordered data mode.
If I run /sbin/tune2fs -l /dev/ida/c0d0p8 I see
tune2fs 1.26 (3-Feb-2002) Filesystem volume name: / Last mounted on: <not available> Filesystem UUID: 21301280-5b21-11d5-9ed2-b7f85f4cdd21 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 262752 ... etc
I tried numerous things such as booting from the cd, then
tune2fs -O^has_journal /dev/ida/c0d0p8
fsck.ext2 -f /dev/ida/c0d0p8
mounting /dev/ida/c0d0p8
deleting .journal
unmounting
/sbin/tune2fs -j /dev/ida/c0d0p8
/sbin/tune2fs -c 0 -i 0 /dev/cida/c0d0p8
mkdir /x mount -t ext3 /dev/ida/c0d0p8 /x tune2fs -l /dev/ida/c0d0p8
seems to mount cleanly as an ext3 system, but when I reboot it come up unclean again.
I would welcome any thoughts.
paulw
-- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
