Hi, I have created ext3 filesystems on my RH 7.2 boxes. But it is very strange that the root filesystem can't be mountet as ext3. So I have no journaling for this filesystem.
Other filesystem are mounted as ext3 as expected. The following informations should help to understand my problem. [root@linux log]# df -kl Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda1 72777176 902048 71135740 2% / none 256752 0 256752 0% /dev/shm /dev/hda3 2071416 32828 2017544 2% /tst [root@linux log]# cat /etc/fstab LABEL=/ / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 LABEL=/tst /tst ext3 defaults 1 2 /dev/hda2 swap swap defaults 0 0 [root@linux log]# dmesg --> Journalled Block Device driver loaded kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.17, 10 Jan 2002 on ide0(3,3), internal journal EXT3-fs: mounted filesystem with ordered data mode. --< [root@linux log]# ls -al /dev/hda1 /dev/hda3 brw-rw---- 1 root disk 3, 1 Aug 30 2001 /dev/hda1 brw-rw---- 1 root disk 3, 3 Aug 30 2001 /dev/hda3 [root@linux log]# tune2fs -l /dev/hda1 tune2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 Filesystem volume name: / Last mounted on: <not available> Filesystem UUID: 7e53e93b-7843-4832-bf8f-c9f40e69aa1d 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: 9256960 Block count: 18484782 Reserved block count: 184847 [root@linux log]# tune2fs -l /dev/hda3 tune2fs 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 Filesystem volume name: /tst Last mounted on: <not available> Filesystem UUID: b5d17eec-f4a5-4d31-84b9-cf75ba756af7 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal filetype needs_recovery sparse_super Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 263296 Block count: 526128 Reserved block count: 5261 Free blocks: 509647 [root@linux log]# uname -a Linux linux 2.4.18-2SCOREsmp #1 SMP Fri Mar 29 19:34:03 JST 2002 i686 unknown So both filesystems have has_journal feature, this means ext3. But /dev/hda1 (/) has no needs_recovery feature and the filesystem state is always not clean. Do you have any suggestions why RH does'nt handle the root filesystem as ext3? Thank you in advance! Best Regards, Danny Sternkopf -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
