similar to: ext3 and 2.4.10-ac12

I am trying to compile 2.4.10-ac11 w/ the ext3-2.4-0.9.12-2410ac11 patch. I'm getting unresolved symbols w/ ext3 module: cd /lib/modules/2.4.10-ac11; \ mkdir -p pcmcia; \ find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.10-ac11; fi depmod: *** Unresolved symbols in

Hi Maybe you allready fixed this problem but here goes: with ext3-0.9.10 and linux-2.4.10-SMP I get a hang doing the following: # mkdir test # cd test # rmdir ../test # ls There are no problems in ext3-0.9.12 and linux-2.4.10-ac11. Regards -- Lars Munch P.S. plz cc me, as I'm not on the list.

An ext3 update for Alan's latest kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The version of ext3 in -ac kernels currently stands at 0.9.6, so this is a fairly large diff. However most of this code has had a decent amount of external testing via the 0.9.9 patch. The changelog since 0.9.6 is below. Please test it if you can, and all being well we shall ask Alan to merge it a

Hi folks, I successfully installed EXT3 on my non-SMP system. This is a (single) P3-450 with kernel 2.4.10-ac11 with the ext3-2.4-0.9.12-2410 patch applied. Works like a jiffy, although I only converted a single disc (and a not really important one too)! (Oh and this is a SuSE 7.0 system) I'd like to note that the Util-Linux installation is pretty hard to do and can go horribly wrong. In

A new work-in-progress release of the Extended Attribute and ACL patches for ext3 is now available at http://www.moldybread.net/patches/kernel-2.4/ This release is against linux-2.4.10-ac12 with ext3-2.4-0.9.12. Status: Extended attribute sharing now seems stable. Performance problems appear to have been addressed. Known Problems: Error message: "VFS: brelse: Trying to free free

Hello ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -

I've not been happy with the stories about the "stable" 2.4.x kernels. Everywhere I read people saying "not for production use". Would you recommend adding ext3 to 2.2.19 (ext3-0.0.7a) or moving to 2.4.1x and using ext3 there (ext3-0.9.12)? -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen@ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/

Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))

Hello, I have done extensive testing between 2.4.9 and 2.4.9-ac12 with ext3 0.9.6 and 0.9.9. I also tried using both kgcc and gcc-2.96. I have a problem with logging into xdm or starting the gnome-session totally locking up the machine while using ext3 0.9.9. It seems to go away using ext3-0.9.6. During xdm/gnome-session the hard disk is under heavy activity. I have attached my kernel config.

Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))

Today our mailserver froze after just one day of uptime. I was able to capture the Oops on the screen using my digital camera: http://www.stahl.bau.tu-bs.de/~hildeb/bugreport/ Keywords: EIP is at journal_commit_transaction, process kjournald # mount /dev/cciss/c0d0p6 on / type ext3 (rw,errors=remount-ro) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts

hi! I'm using ext3 for a few weeks by now, and i'm quite satisfied, especially in combination with the new quota code in the ac kernels... i never had any fs-errors till now... i upgraded to 2.4.9-ac12 (w/o any additional patches, runs ext3fs 2.4-0.9.6) yesterday, and today i got this errormessage... EXT3-fs error (device ide1(22,66)): ext3_free_blocks: Freeing blocks not in datazone -

Hi I switched over to ext3 a few weeks ago because it was faster to boot when the power has failed (and it fails every day or so...) I was using 2.4.9, everything was right, all my partitions were ext3, including root : VFS: Mounted root (ext3 filesystem) readonly. I switched over to 2.4.10, with the right patch, and now : VFS: Mounted root (ext2 filesystem) readonly. whatever I try to do... even

Hi, After mounting -t ext2 an ext3 partition, working with, do I have to recreate .journal when I remount the partition as ext3 ? Thanks ! Liu

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes

Patches against 2.4.10-pre4 and 2.4.9-ac9 are at http://www.uow.edu.au/~andrewm/linux/ext3/ It's a fairly large change. The most significant parts are * the inclusion of Stephen's error-handling work, which is designed to remount the fs read-only in the presence of software and hardware errors, rather than forcing a panic. * Stephen's fix for the journal_revoke assertion

Good morning, I try to use the last release of ext3 patch with a 2.4.10 linux kernel. I have two troubles : - when the kernel is booting, I receive : NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 208k freed Adding Swap: 128480k swap-space (priority -1) Adding Swap: 128480k swap-space (priority -2) Why my root

Hi, I just attempted to convert my only partition, /, to ext3. I downloaded the patch and compiled the kernel with ext3 support built-in, along with the JBD Debugging support. Compiled the kernel and rebooted, everything was fine. Did a tune2fs -j /dev/hda2 on the partition in single-user mode, with e2fsprogs 1.24a. It complained about not having enough space, or something like that, (I have

Hello, The 0.9.9 2.4.10pre4 patch doesn't apply. There are 5 rejects. The first three are easy to fix, but the fourth in vmscan.c will be very difficult without being a developer. The fifth I am not sure about. This brings up the fact that many of us are using ext3 and have to patch every time a new kernel comes out. I really think we need to strong arm Linus or something and get

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup: