Skip to contentSkip to conversation

Ext3+ramdisk journaling problem

DISCUSSION Xin Zhao 3 participants 3 messages Apr 25, 2005 – Apr 27, 2005

lore
Share & tools
lore

Xin Zhao

author
#0 lore raw

hi,

I used ramdisk as an ext3 journal and mount ext3 file system with option data=journal. It worked fine and speedup the ext3 file system. However, After I reboot the system and try to mount that ext3 filesystem, the system reported:

mount: wrong fs type, bad option, bad superblock on /dev/hda2,
or too many mounted file systems

This gave me a feeling taht the ramdisk is not a right journal anymore. Any solution to this problem? Also, how to ensure that the journal stored on the ramdisk is committed to ext3 filesystem before it is umounted? Any commands to do this?

THanks in advance for your kind help.

Xin

#1 lore raw
Quoted 4 lines · Xin Zhao

hi,

I used ramdisk as an ext3 journal and mount ext3 file system with option data=journal. It worked fine and speedup the ext3 file system.

Uhh, the whole point of a journal is that when the computer goes down hard and doesn't have a chance to clean up. If you put the journal on a ramdisk, you might as well just mount it as an ext2 filesystem and be done with it. Without the journal _on_disk_ you get no data or filesystem reliability advantages. If you're after speed, just forgo the reliability or buy better disks.

Cheers,
Kyle Moffett

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a18 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$ L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+ PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r !y?(-) ------END GEEK CODE BLOCK------

#2 lore raw
Quoted 8 lines · Kyle Moffett
Quoted 4 lines · Xin Zhao

hi,

I used ramdisk as an ext3 journal and mount ext3 file system with option data=journal. It worked fine and speedup the ext3 file system.

Quoted 7 lines

Uhh, the whole point of a journal is that when the computer goes down hard and doesn't have a chance to clean up. If you put the journal on a ramdisk, you might as well just mount it as an ext2 filesystem and be done with it. Without the journal _on_disk_ you get no data or filesystem reliability advantages. If you're after speed, just forgo the reliability or buy better disks.

Alternative: Buy a real ramdisk with battery-backup instead of using a "ramdisk" in system ram. Such a thing will last across a reboot, offering both nice speed and all the comforts of a journal.

Helge Hafting