similar to: Ext3 compile problem on 2.4.13

I have gotten the 2.4.13 kernel and the 2.4.13 ext3 patch. Unfortunately, it appears that some lines are wrapped, meaning that the long lines are actually on two lines, which throws the entire patching process off. Right now, my only recourse is to go through and manually fix the problem, which will take awhile, since there are more than 17000 lines of code! Is the problem on my end, or on the

Hi all, Thanks for the prompt reply about 2.4.13. I applied the patch after I'd applied the win4lin and mki patches and it fails. The .rej file is included after this message. If you need any further info I'll try and supply it. Thanks Robyn This file is sched.h.rej from /usr/src/linux/include/linux/sched.h.rej *************** *** 399,404 **** u32 self_exec_id; /*

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, I just wanted to compile my kernel 2.4.13 with the ext3-2.4.13-pre6 patch, but it doesn't work. It seems, that the patching failes by replacing some things in a textfile. Does anyone of you know, if there is a upcoming solution for this? Kind regards Jan Albrecht -- Jan Albrecht Phone: +49-5241-80-88404 System Consultant UNIX/NT Fax:

Hiya, Now that 2.4.13 has been release, any word on how stable ext3 is on this? Hope they haven't broken anything in the vm again....;) I'm currently running 2.4.8 and I'm very happy with it and given the nightware over the past few releases, just wanted to find out what the state-of-play is at the moment. -=David=

I am running Debian Potato with kernel 2.4.27-rc3 on a Sparc Server 20, 128MB RAM machine. After few hours I get the following error in the syslog kernel file Jul 15 01:09:25 mudshark kernel: Assertion failure in journal_stop() at transaction.c:1418: "journal_current_handle() == handle" Jul 15 01:09:25 mudshark kernel: kernel BUG at transaction.c:1418! Jul 15 01:09:25 mudshark kernel:

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, I've tried to compile an ext3 extended 2.4.5 kernel but I got no luck. After applying the ext3 patch from the gkernel/ext3 (download today) (symlinks are created) I run into following problem: gcc -D__KERNEL__ -I/usr/local/src/kernel/linux-2.4.5-ext3cvs/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -DEXPORT_SYMTAB -c ksyms.c

Hello, Stephen, It seem that in the presence of several jornalling file systems in the kernel some mechanism is needed for proper sharing of the ->journal_info pointer in the task_struct. One journalled file system can indirectly call another during page fault in copy_from_user, quota file modification, or __alloc_pages()->balance_classzone()->shrink_cache()->vm_writeback()

For the past few weeks, I have been getting 403 access errors on http://www.uow.edu.au/. Has anyone else been experiencing that? -- -- Skylar Thompson (skylar@attglobal.net)

I am having major problems on one of my file-servers. I have the root filesystem on an Ext3 software RAID 1 between four SCSI drives. It had been running for about two months without problems, but today I found it was having some trouble with unlinked inodes and I/O errors on certain files. I took it down to single-user mode, and ran fsck on it. That operation mixed up files like /etc/hosts with

This patch finally gives us full proper -ENOSPC handling for btrfs. Now whenever you do a btrfs_start_transaction, you must specify the number of items you are planning to add/delete/modify. The worst case number of blocks that could be modified by changing that number of items will be calculated and checked against the amount of free space in the space_info where the root you are modifying

I have tried everything to compile a new kernel on my 7.2 base system. I have used 2.4.13-ac6 and 2.4.13 w/ ext3 patch. I have compiled with ext3 built-in and with ext3 as module (with the initrd). I have a SCSI system so I have done the previous variations with both SCSI support built-in and modular (with the initrd). The error I get is: Remounting root filesystem in read-write mode: mount: no

Hello everyone. I'm running Red Hat 7.3 with kernel 2.4.18-10 and all errata patches installed. My system has been running for over three years without any problems. All I've done to it in that time is add a mirror set of two 80GB drives, a Promise IDE controller, and upgrade Red Hat through the 7.x series. Right now I have three drives. A 13GB system drive off the motherboard, and

imq and htb are used to control traffic. When I create a bridge with the bridge-utils, I get a new device : br0. I can shape traffic on this device, but I can not use iptables to mark packets. I used ipmode http://www.linuxvirtualserver.org/~julian/#bridging my kernel is 2.4.19 when i compile kernel I get the following error: br_forward.o error 1 first_rule error 2 if I used ipmode, then I can

With 2.4.28 and Julian Anastasov''s http://www.ssi.bg/~ja/routes-2.4.27-9.diff patch, I get the following when I attempt to build my kernel. Any ideas? Thanks! gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -fno-unit-at-a-time -nostdinc

If I patch the 2.4.14 kernel with the grsecurity patch first I get errors while patching the ext3 patch. the link for the grsecuritypatch is http://www.grsecurity.net/download.htm (which ever patch I do first works fine..the onther patch fails) this is the error I get fro patching the ext3 patch second (I get an error inthe same place if I patch the grsecurity patch second) Hunk #1 FAILED at

Renewed shall be blade that was broken/The crownless again shall be king.'

Hello, We have about 20 - 30 embedded machines running Linux 2.4.13, which the ext3-2.4-0.9.13-2413 patch applied. These are PowerPC 7410 based systems. I am getting reports of Oops happening either during removes (rm's), or coppies (cp's). Most reports state that issuing the same command once the system boots back up, does not cause it to crash. I guess its something else leading up

Hello anybody, I have a Suse 7.2 Linux with Kernel 2.4.9, which is compiled by myself, and is running stable. Now I try to patch my sourcecode in the way you write on your homepage. But thier are two Proglems: 1. When I download the the file "ext3-2.4-0.9.6-249.gz" with my Windows, I get no packedfile, I get a Textfile?! -so gunzip would not work. 2. never the less, I tried to patch