Ext3+ramdisk journaling problem

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: Ext3+ramdisk journaling problem
    • From: Kyle Moffett <[email protected]>

• Prev by Date: Re: [PATCH][RFC][0/4] InfiniBand userspace verbs implementation
• Next by Date: Re: Git-commits mailing list feed.
• Previous by thread: Re: PATCH-remove experimental depends from forcedeth
• Next by thread: Re: Ext3+ramdisk journaling problem
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]