Bug 20501
Summary: | some problem message | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat High Availability Server | Reporter: | angus young <angus> | ||||
Component: | ext3 | Assignee: | Stephen Tweedie <sct> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Wil Harris <wil> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | beta | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i586 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2000-12-07 00:21:08 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
angus young
2000-11-08 00:03:02 UTC
Created attachment 5141 [details]
dmesg
The messages ext3: No journal on filesystem on 08:01 EXT3-fs: get root inode failed are the result of the linux VFS trying to mount the root filesystems (first the initrd, and then your real main root filesystem) first as ext3. That failed, because root was in fact ext2, so the VFS then tries ext2 which succeeds. It's not a bug or a problem, but a side-effect of the fact that there has to be some way to allow the root filesystem to be ext3. I'll look into the kdb messages, but kdb is only a debugging module and will most likely not ship in any production ext3 kernel. thanks for you explanation. so there is a modification for convert (this is not the good word) an ext2 to ext3 when the filesystem is the root filesystem. I use actually reiserfs and there is a similary think to know, a root filesystem must be mount with notail option. Not yet, but there will be. Right now you have to use the mechanism documented on the ext3-users list, using lilo to pass the journal creation root flags to the kernel. ok, i will do that. I hold you to inform. highly ext3 with metadata only ;-) some benchmark result (bonnie++ 1.0d) mke3fs /dev/sda1 mount -t ext3 /dev/sda1 /mnt/ext3 cd /mnt/ext3 ~david/bonnie++-linux-libc6 -u 0:0 Version 1.00d ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP localhost 496M 2198 64 5176 11 3674 11 3696 98 12324 9 11.5 0 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 30 194 96 705 99 4225 95 203 99 869 98 278 38 localhost,496M,2198,64,5176,11,3674,11,3696,98,12324,9,11.5,0,30,194,96,705,99,4225,95,203,99,869,98,278,38 cd / umount /dev/sda1 mkfs.ext2 /dev/sda1 mount -t ext2 /dev/sda1 /mnt/ext3 cd /mnt/ext3 ~david/bonnie++-linux-libc6 -u 0:0 Version 1.00d ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP localhost 496M 3486 98 14004 18 5013 12 3660 97 12293 9 15.6 0 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 30 204 99 716 98 4716 99 207 99 912 99 495 66 localhost,496M,3486,98,14004,18,5013,12,3660,97,12293,9,15.6,0,30,204,99,716,98,4716,99,207,99,912,99,495,66 it will be interesting to compare with ext3 metadata only but I cannot mount my root partition in ext3 this is my procedure: dd if=/dev/zero of=/journal.dat bs=1k count=10000 chattr +i /journal.dat ls -i /journal.dat 2437 :journal.dat /sbin/lilo -R ext3 rw rootflags=journal=2437 reboot kernel error before scsi module loaded this is my lilo.conf boot=/dev/sda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux image=/boot/vmlinuz-2.2.16-22 label=linux initrd=/boot/initrd-2.2.16-22.img read-only root=/dev/sdb1 image=/boot/vmlinuz-2.2.17-6 label=ext3 initrd=/boot/initrd-2.2.17-6.img root=/dev/sdb1 and this is /etc/fstab LABEL=/1 / ext2 noatime,nodiratime 1 1 /dev/sda10 /home ext2 defaults 1 2 /dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner 0 0 none /proc proc defaults 0 0 none /dev/pts devpts gid=5,mode=620 0 0 /dev/sda8 swap swap defaults 0 0 #/dev/sdb3 swap swap defaults 0 0 /dev/sda3 /mnt/c: vfat defaults 0 0 /dev/sda5 /mnt/d: vfat defaults 0 0 /dev/sda6 /mnt/e: vfat defaults 0 0 /dev/sda7 /mnt/f: vfat defaults 0 0 /dev/sda1 /mnt/ext3 ext3 defaults 1 0 should i modify "dij`" ext2 to ext3 in fstab for root partition /dev/sdb1 ? See the comment above: there is no clean mechanism for now for converting root to ext3 if you are booting via initrd. There will be in a subsequent e2fsprogs package. The method will be documented once it becomes available. All of the boot warning messages should be fixed in 0.0.5c. Mounting root as ext2 should no longer produce odd ext3 messages, and the recovery messages will not occur on ext3 root filesystems after a clean reboot. kdb messages are from a debugging module which is not part of the core of ext3. |