similar to: turning off journaling on the fly?

A few wild ideas/questions : 1) Is there a way to check the size of the journal of an ext3 filesystem ? I mean - the actually used size ; not the total size of the journal. 2) Would it be difficult to implement "freeze" of ext3 filesystem - that is, blocking all I/O to the filesystem until it's "unfrozen" (XFS can do that), for two purposes : A/ allowing

Hi, I'd like to use a flash drive as a journal device, with the purpose of keeping the main disk drive spun down as long as possible. I have a couple of questions: 1) Does the journaling code spread write accesses to the journal device evenly, as I hope, or are there blocks that are particularly "hot"? I.e., do I have to worry about the flash device dying quickly because of

Are there any good options to configure a filesystem so most activity takes place in the RAM buffer with the flush to physical media allowed to lag very far behind? OpenNMS does some data collection that keeps the disk very busy. I don't want to lose the history completely in a crash like you would with a ramdisk, but it wouldn't be a big problem if only the last 10-30 minutes would

Hi, I am using ext3 file system. Can I know the place where journal log is stored and more details about journaling. Quick response is appreciated. Thanks in advance, Mallika. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20041227/574c90bf/attachment.htm>

[ If this is explained somewhere else (HOWTO or FAQ), please give me a pointer. ] Is there any way to mix loop-device (and in particular) loop-AES and ext3 together in data journaling mode? Ie. bottom -> to -> top ext3 - loop-AES - ext3 raw - loop-AES - ext3 Or am I shooting myself to leg, I am? BR, Jani -- Jani Averbach

Hi, well I've deployed ext3 on two machines already and so far it does its job excellently at no (for me) noticable performance loss. I hope it gets incorporated into stock kernels by Linus soon. Anyways I've been hearing about ext3 supporting full-data journalling on a per-file basis but couldn't find any detailed info about it. Even tried grep'ing throught the source. How

I am trying to use data=journal on my root file system. I have separate slices on which journal=data works fine on all of them, except root. I have tried putting rootflags=journal=data on my kernel line in Grub, but I get a kernel panic. I'm missing something simple, I jut know it. It can't be the kernel version because it works on the other slices. My etc/fstab file is as follows:

Hello, I've attached the output from "sh scripts/ver_linux" per the bug reporting guidelines, and a diff of the file fs/jbd/transaction.c. At this point, I'm trying to hunt down why some system threads, which are executing the Lustre file system code, are taking an unexpectedly long time executing various ext3 file system functions. I added some debug code to these system

Hi, I'm formatting a flash with ext3, but I need to move the journaling file (/.journal) in the flash to prevent it's corruption. In previous message I read that it's possible (https://www.redhat.com/archives/ext3-users/2004-March/msg00009.html), but I can't find any /.journal in my ext3 fs. How can move the journaling file in the flash without /.journal file?? Thanks

Hi, We are currently doing SpecSFS comparison benchmarking to evaluate advantages of FS journaling to NVRAM card versus journaling to hard disks. We compare NFS performance for Linux file server with ext3 file system in ?data=journal? mode for three different locations of the file system journal: - inside main file system - on a dedicated HD - on an NVRAM PCI card The file system is

Forgive my novice question, but I am a new student of Linux working on presenting the ext3 journaling filesystem to my class. I seek any advice on how to visibly demonstrate (including a purposeful crash of a Linux box) the benefits of ext3 over ext2. I am not worthy to lick the bootstraps of this group, but I beg for any help! The problem I am having extends to even locating the .journal file

https://bugs.freedesktop.org/show_bug.cgi?id=101404 Bug ID: 101404 Summary: GTX 970M (GM204-A) not powered off when not in use (DynPwr in stead of DynOff) Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium

Hello what is the limitation of inode and journaling on 32 bit ext3 file system. what about 64 bit. Thanks

Hi there, I installed my mandrake linux 8.1 with reiserfs. I would like to use wine without my windows partition. Now I see the following text in the wine man-page: --- format: Filesystem=<fstype> default: "win95" Used to specify the type of the file system Wine should emulate on a given directory structure/underlying file system. Supported types are "msdos" (or

EXT3 developers: I am curious, if EXT3 is currently being used on the root partition in "data=ordered" mode (the default as I understand), and I want to have the it come up in data=journal mode, how do you effectuate this conversion? I would also be curious how to know if anything special is required for doing so for the /boot partition as well. I believe that with the /home partition,

Hello, Is there some document about ext3 performance tuning and choosing the right type and size of journal? Except RedHat's white paper. From what I read I understood that for typical operations data=ordered is prefered. For the cases when there are many writes not appending to files data=journal is the choice. And if I want to get the most performance or in case where program is doing

Hi. I'm using e2fsprogs 1.23 on a Roswell system with a patched 2.4.7 kernel (using patch ext3-2.4-0.9.5-247) and am trying to create an ext3 filesystem whose journal is located on another device. The incantation I'm trying is: mke2fs -j -J device=/dev/hdc2 /dev/hdc3 I keep getting an error along the lines of "mke2fs: Journal superblock not found". I've tried creating

Hi all, Man page of tune2fs says that max journal size is 102,400 filesystem blocks, which translates to ~100MB with 1kb blocks or ~400MB with 4kb block. I wonder - why this limitation exists? Now that relatively cheap ssd devices exist (gigabyte iRam) that offer up to 4GB of space, it would be extremely useful to use whole capacity of such device for full data journaling. -- Jure Pe?ar

How come if I install a fresh redhat 7.2 system and change fstab from defaults to data=journal for the / file system, it breaks everything? Thanks, --------------------- Gabe E. Nydick Systems Lead ClubPhoto, Inc. P: 408.423.6611 F: 408.557.6799 ----------------------

A scsi error (caused possibly by a loose cable) has left the processes accessing my ext3 file system hung in an unkillable state after it triggered an assert in ext3's journaling layer. I assume my only recourse at this point is to reboot. Please correct me if I'm wrong. Log messages appended. Thanks, -Jim Nov 21 04:04:04 attila kernel: SCSI disk error : host 0 channel 0 id 5 lun 0