similar to: External Journal scenario - good idea?

Hi there, I started getting errors on one of my 2 drives, so I got a warranty one. Then I made an exact copy of the failing one onto the new one with dd, and swapped them. I ran fsck on all the affected partitions, and things looked good. Then I started using the striped RAID device (ext3) which had some minor data loss (mostly under big files), and I got the problems with the journal. The

I have a raid5 array on my web server for which I am currently considering a move to ext3. I want to use an external journal to improve performance. Since the external journal would reside on a drive that is not participating in the raid array, I'm wondering what the behavior of an ext3 filesystem is should the device an external journal is on should fail. If it reverts to ext2

I have been playing with external journals some more and thought I should share some experiences. I am running 2.4.16 with the ext3 patches from Andrew Morton and e2fsprogs 1.25 I have an ext3fs filesystem on an 8 drive RAID5 array and place the journal on a partition of the mirrored pair that I boot off (all drives SCSI). I have tried pulling the power cable and seeing what happens. I finally

Hi Ted and all, I have a couple of questions near the end of this message, but first I have to describe my problem in some detail. The power failure on Thursday did something evil to my ext3 file system (box running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms are very similar to what Eddy described

Hello I try again. Can anybody of you acknowledge or not if mode data=journal in ext3 is safe to use in Linux kernel 2.6.x? Wee need to have a very consistent and integrity for our filesystem, and it would then be desired to journal both data and metadata. But if this mode can corrupt the filesystem as both Phil White and Nicolas Kowalski has experienced, it may be more advised to use mode

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>

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

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

Today, I had to uncleanly shutdown one of our machines due to an error in 2.6.28.3. Durin the boot sequence, the ext4 partition /home experienced a journal replay. /home looks like this: /dev/mapper/volg1-logv1 on /home type ext4 (rw,noexec,nodev,noatime,errors=remount-ro) Filesystem Size Used Avail Use% Mounted on /dev/mapper/volg1-logv1 2,4T 1,4T 1022G 58% /home Filesystem

Hi, I tried to convert my root partition from an ext2 to ext3 fs using tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal

[NOTE: I apologize in advance if this shows up as a duplicate. I sent it once by accident from the wrong account, so the message has been waiting moderation. If the moderator reads the list, hopefully they'll notice I already posted :)] I have a number of machines which are used for mail storage. We've had issues with sporadic slow connections to the machine, seemingly blocking on I/O.

journal.c: In function 'guestfs__journal_get': journal.c:120:9: error: #pragma GCC diagnostic not allowed inside functions journal.c:121:9: error: #pragma GCC diagnostic not allowed inside functions journal.c:123:9: error: #pragma GCC diagnostic not allowed inside functions make[3]: *** [libguestfs_la-journal.lo] Error 1 Signed-off-by: Olaf Hering <olaf@aepfle.de> --- Not compiled.

Hello, I have some performance problems in a file server system. It is used as Samba and NFS file server. I have some ideas what might cause the problems, and I want to try step by step. First I have to learn more about these areas. First I have some questions about tuning/sizing the ext3 journal. The most extensive list I found on ext3 performance tuning is

Errors happy in the early hours of the Morning 4 or 5 AM. every time , many directories and files can't be accessed , message "I/O error " display, all partitions become read-only no data lost and no data can be wirted ,only redress is a reboot. Distribution: REDHAT version 4 X86_64 update 5 Server Platform : IBM X 366 RAID Controller : IBM ServerRAID 8i Disks : 4*73G SAS

Since systemd 209, all the functionalities of the former libsystemd-* (including libsystemd-journal) have been merged into a single libsystemd, with the former libraries left as compatibility ones. Thus, first look for libsystemd, and if not found try again with the libsystemd-journal as used before. --- configure.ac | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff

Hi, I've just recently noticed that the ext3 projects is being actiavely maintained (again?). And looking at the new pages for 2.4.x it really made me interested. But I've got a few small questions I'd like to clarify before I start to use it. 1) Tune2fs and mke2fs talk about a "default journal size" that is depending on the partition size but don't give

Is there a way to get usage statistics on the journal device? We are testing battery-backed NVRAM cards with extremely busy 1.7TB filesystems (mode data=journal) and we need to figure out what size NVRAM card we need. I assume the journal size depends on how much writing you are doing and we can do simple theoretical calculations (writing 2.5MB/s, 60 seconds of journal would be max 150MB), but

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

On 2013-06-26, at 9:38 AM, Eric Sandeen wrote: > On 6/25/13 3:13 AM, Folkert van Heusden wrote: >> >> I have a system with an ext4 filesystem with its journal on an other >> device (an SSD). >> Now this SSD dropped of the sata bus so the filesystem went r/o. >> I would like to remove the journal but it says it can't because >> needs_check is set. >

Greetings, I recently cpio-ed some user directories onto a new ext3 partion. After putting this file server's partition into production, I noticed a .journal file in the root directory of the partition dated well before the creation of this partition. I think this .journal file was copied over from the old filesystem and I am concerned that I over-wrote this current filesystem's