similar to: Kernel 2.4.5 and gkernel/ext3 CVS: cannot compile

Hello everyone and Timo in particular, about a year ago I implemented a SHA-1 variant of the HMAC(-MD5) present in Dovecot. I had always disliked this a bit, because it replicates a lot of code. This patch generalizes the HMAC function to take a hash_method struct as parameter, and changes existing code which uses the "old" HMAC function to use this new one. I'm not really sure

Hi ! Compiling kernel linux 2.4.10pre4 without ext3 works. After patching the kernel sources with cd /usr/src/ext3 scripts/add-to-kernel.sh scripts/file-manifest linux compile fails: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DEXPORT_SYMTAB -c

Hi - if I have a doubly patched kernel (2.4.5) (1) Apply gkernel/CVS ext3 patches (2) Apply Neil Brown/Reiserfs team knfsd and reiserfs patches Will ext3 be exportable by knfsd (i.e. inherit automagically the nfsd_operations thingies from ext2) or does it need further patching? -- Chan Shih-Ping (Richard) <cshihpin@dso.org.sg> DSO National Laboratories 20 Science Park Drive

Hello Since 2.4.20, we have problems with ext3. Machine is 2xPentium III (1GHz), 2GB RAM, 1GB swap. RH 8.0 (glibc-2.3.1-21), gcc (GCC) 3.2 20020903 We have a lot of users: oceanic:~# wc -l /etc/passwd 6694 /etc/passwd connected via SAMBA (2.2.7) from 200-300 Windows-XX workstations Partition with ext3 looks like this: oceanic:~# mount |grep ext3 /dev/sdb5 on /home1 type ext3

OK, I''ve been fritzing around with something I noticed last night, thinking that I understood what was going on, but now it''s getting confusing again. A system that has been running for a couple of months had a hole in the probe ID list near the end in the middle of the fbt probes. And then a couple of syscall probes were stuck in the hole. It looked like this: ... 40311

Well I decided that 2am on a thursday night would be a good time to try this and I've hit a wall... most of the other errors were pretty easy to fix. I just don't understand this one: --snip--snip--snip-- gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -D__linux__ -pipe -fno-strength-reduce

Anyone try this yet? ftp://ftp.valinux.com/pub/software/kernel/beta/2.4.5-beta2va3.11/ List of SRPM contents follows. -- TheBS atomic-lookup.patch atomicalloc.patch byteprofiling.patch comtrol-1.23.patch configs-2.4.5.tar.gz copy-user-reschedule.patch dac960-enclosure-quiet.patch dma-livelock-fix.patch e100-1.5.5.tar.gz e1000-3.0.7.tar.gz eepro100-speedo-1.patch emu10k1-tone.patch

Hello, Is an version from ext3 available for the 2.4 kernels's ??? My second question is, give it a anon CVS server for live update the sources ?

Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had

> > 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. >

Red Hat 2.2.19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k

I reported this previously and it was verified. Is this a bug in netlink or what? Who should I report this to? Original Oops report: http://mailman.ds9a.nl/pipermail/lartc/2004q2/012614.html Thanks. Linux rebecca 2.6.4 #1 Mon Sep 27 15:16:48 EDT 2004 i686 GNU/Linux Sep 27 19:02:58 rebecca kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Sep 27 19:02:58

There are several files that: #include "linux/file" not #include <linux/file> #include "asm/file" not #include <asm/file> Here's the little script that converted them: egrep -i -r -l --include=*.[ch] \ "^[[:space:]]*\#[[:space:]]*include[[:space:]]*\"(linux|asm)/(.*)\"" * \ | xargs sed -i -e

There are several files that: #include "linux/file" not #include <linux/file> #include "asm/file" not #include <asm/file> Here's the little script that converted them: egrep -i -r -l --include=*.[ch] \ "^[[:space:]]*\#[[:space:]]*include[[:space:]]*\"(linux|asm)/(.*)\"" * \ | xargs sed -i -e

Ah, Mondays. The following oops happened after approximately eleven days of uptime. The machine was not under any particular load at the time. Following a forced reboot, all filesystems replayed the journal successfully. Relevant log entries leading up to the oops: Nov 4 04:54:08 localhost kernel: attempt to access beyond end of device Nov 4 04:54:08 localhost kernel: 03:02: rw=1,

Hi, oops in iput - Kernel 2.2.19/i386 + ide-udma patches + ext3 patches (0.0.7a) Intel BX chipset, SCSI Disks Symbios chipset - The crashing process is the master process of "postfix" an MTA. Just before the crash all processes on that machine started to segfault in nameserver resolution (remote dns server) and after 2-3 minutes this oops happened. ksymoops 2.3.4 on i686 2.2.19.

Hi, By running some scripts on our target system for a while, I lost all means of access to the system. It seems that the kernel is crashed with the following error message: Assertion failure in do_get_write_access() at transaction.c:731: "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)" Oops: Exception in kernel mode, sig: 4 We are currently running Linux version

I am having some trouble compiling ext3 for the 2.4.13 kernel. It appears that the journaling source file is corrupted: In file included from sysctl.c:33: /src/linux-2.4.13/include/linux/jbd.h: In function `buffer_jbd': /src/linux-2.4.13/include/linux/jbd.h:241: `BH_JBD' undeclared (first use in this function) /src/linux-2.4.13/include/linux/jbd.h:241: (Each undeclared identifier is

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

Hello, I've got a rather strange setup over here with about 6 ext3 partitions, one 50gig lvm partition and one 2 gig software-raid1 partition running under a heavily patched 2.4.10 kernel (various netfilter patches, freeswan, current lvm patch (1.0.1-rc4 and current ext3 patch). Furthermore I have all of those neccessary filesystem tools, so don't tell me to upgrade :-) The machine was