similar to: ext3 kernel patch for kernel 2.4.7

-----Original Message----- From: 박노희 [mailto:nohhee@turbolinuxsystems.com] Sent: Tuesday, July 31, 2001 1:35 PM To: 'ext3-users-admin@redhat.com' Subject: ext3 problem? Please give me advice about the following problem. A few days ago, I lost some of oracle DB data on my server. My server was running Oracle DB and HA(high availability) server for web service. The filesystem was ext3,

I have a DB server running ext3 under fairly extreme load. The system is a Dell 2550 (Dual P-III 1Ghz with a gig of RAM) running RedHat 7.2 with the stock 2.4.7-10 kernel. Things have been swell for 95 days, but I just got bit: Linux 2.4.7-10smp #1 SMP Thu Sep 6 17:09:31 EDT 2001 i686 unknown [root@ root]# cat /root/oops.20020817 kernel BUG at journal.c:373! invalid operand: 0000 CPU: 1 EIP:

I thought I'd summarise this with a proper subject line: 1. We used up2date to upgrade the kernel of a 7.2 machine that is doing far too much journalling (kjournald at 50% CPU+ often). 2. It installed fine, but when we reboot - GRUB only shows the old 2.4.7-10 although there are 3 kernels listed in grub.conf My Question is "How can we select booting to 2.4.18-24.7 when GRUB lonly lists

Hello, Sir. My name is Hiroyuki Kudo. I have a problem using ext3 in my system DELL PowerEdge 1550. I recently installed RedHat 7.2 (kernel-2.4.7-2) and found that it used ext3. Later, since I needed to use nfsv4, I got kernel-2.4.4-nfsv4. But it didn't start up and saying `kernel panic` What is wrong with it? If the problem can be cleared with ext3-patch, how can I do it?

Hello , I use kernel 2.4.7 patched with corresponding ext3 patch. The problem I have is that when I startup I get a panic in a kernel. I started to debug util-linux and found that mount does a segmentation fault when trying to open /etc/mtab file. The segmentation fault ocurrs on open() call inside mtab_is_writable() procedure: printf("mtab_writable: pass 1\n"); if (ret ==

Hello, I am using kernel version 2.4.7-10 I upgraded one of the ext2 partition to ext3. the partitions are nearly empty. I ran a program to create empty files, having names in lexicographical order. The time taken to create empty files (100 .. 100000) is same on an ext2 partition and a ext3 partition. Can anyone pls. tell me why there is no difference in the time taken. Is the htree algo.

Hi, I just noticed that my file server running 2.4.18-pre3 + IDE patches & NTFS patches has this error message in the logs: EXT3-fs error (device md(9,4)): ext3_free_blocks: Freeing blocks not in datazone - block = 33554432, count = 1 This is the only ext3 error I have seen and the uptime is currently over 74 days. The error actually appeared two weeks ago. The timing coincides well with

Hello all. I was playing with tune2fs to see how large the .journal file should be on a 17G partition with 512M ram (it's 32M, by the way). I am using plain 2.4.7 with ext3-2.4-0.9.4-247, compiled with gcc-2.96-85 on a RH7.1 distribution with the relevant changes, i.e. e2fsprogs-1.22-1, mount-2.11g-4 and util-linux-2.11f-3 taken from rawhide. I don't have any ext3 statement in /etc/fstab,

Hi, I am using an ASUS CUV4X-E mother board with a scsi adapter Adaptec AIC-7881U, with one QUANTUM ATLAS_V_18_WLS and MAXTOR 4K040H2, ATA DISK drive connected with a VIA vt82c686a (rev 22) IDE UDMA66 controller. The instalation from original kernel 2.4.7 was ok, but when I upgrade to kernel 2.4.9-31, almost every day I got an error in many process, including apacha, qmail and many

Hello After compiling and booting a RH 8.0 box with a 2.4.19 vanilla kernel i've started to experience some problems on my /home partition, (i/o errors on 2 files). After rebooting the machine failed the to mount /home and dropped me in the recovery shell. The fsck is still running after 9 hours. The system is a dual athlon MP with 1Gb ram and ASUS MB. the /home patrition is mounted on 3 120

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

I am running 2.4.18-3. I am getting terrible performance. I noticed in the boot.log that my / fs is ext3 and my kernel does not support ext3. I have tried to recompile the kernel with ext3 support. It did not seem to work. (e.g. lags for 40 or so when i am unzipping multiple files) Firstly, is this likely to be the case of my problems? How can i fix it? Do I just recompile the kernel or do I need

Hi, I had ext2 and 2.4.7 kernel , quotas were working ok. Now when all my filesystems are ext3 I figured out that quotas are not working.... if I do quotaon , repquota, quotacheck the programs return 0 without any output..... Does ext3 supports quotas? Nikolai

Hello ext3-users, I tested ext3 on a Linux for S/390 with several stress and benchmark test tests and faced a kernel bug message. The console showed the following output: Message from syslogd@boeaet34 at Fri Aug 3 11:34:16 2001 ... boeaet34 kernel: Assertion failure in journal_forget() at transaction.c:1184: "! jh->b_committed_data" I tried the Patch from

> > Hi, > > I'm running a 2.4.18-14 kernel with a heavy IO profile using > ext3 over RAID 0+1 volumes. > > From time to time I get a black screen stuck machine while > trying to umount a volume during an IO workload (as part of a > failback solution - but after killing all IO processes ), > with ping still responding, but everything else mostly dead. >

Hi, I am trying to compile the kernel with ext3 support and i downloaded the 2.4.13 kernel and patched it for RH 7.2 to update from the 2.4.7 precompiled ext3fs kernel. Then i selected ext3 support and and the JBD debugging support under 'make xconfig.' Then i ran the following commands make clean make dep make bzImage make modules make modules_install cp arch/i386/boot/bzImage

Hello All, I am running Linux 2.4.7-10, 2.4.18-4 and 2.4.19-pre9, I see the following oops quite often (mainly on 2.4.19-pre9 with kdb). All the kernels I use have the kdb patch installed. 1 kmem_cache_alloc (offset 0x125) get_unused_buffer_head journal_write_metadata_buffer journal_commit_transaction kjournald kernel_thread kmem_cache_alloc dis xchg %eax, (%ebx) cmp $0x5a2cf071, %eax (where

Rebooting to try 2.4.7-ac4, I had Xfree86 crash on exit and hang the machine (it does that once a month or so; this notebook gets booted quite often). After fscking the root and another ext2 partition, the system got to the big ext3 partition and just went dead. No message, no disk activity, no keyboard response. I powered down and rebooted 2.4.7-ac3 patched with ext3-2.4-0.9.5-247ac3, and that

My system is RH7.2 with custom 2.4.18 or 2.4.19 kernel(s), downloaded from kernel.org. My root filesystem is ext3 on ataraid. I'm using initrd. My system comes up fine with 2.4.18 kernel, but when trying to boot a new 2.4.19 kernel I get the following sequence:

My Dell server was preloaded with Redhat 7.2 , Linux 2.4.7-10, gccv2.96 with Ext3 file system. I want to install the machine into my company W2k domain using winbind but my Linux kernel does not support the needed ACls. I Does the latest Linux kernel come with ACL support and if so should I just update the kernel to 2.4.19 which I think is the latest production quality kernel? The ACL