similar to: Ext3 on NON-SMP system

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

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 :-))

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 :-))

Does anyone know if the 2.4.10-ac11 ext3 patch applies cleanly to 2.4.10-ac12? If so, do you think it's safe to use? Thanks!

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 -

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

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

An ext3 patch against linux 2.4.10 is at http://www.uow.edu.au/~andrewm/linux/ext3/ This patch is *lightly tested* - ie, it boots and does stuff. The changes to ext3 are small, but the kernel which it patches has recently changed a lot. If you're cautious, please wait a couple of days. The patch retains the buffer-tracing code. This will soon be broken out into a separate patch to make

Hello all, We recently switched to kernel 2.4.10 from kernel 2.4.4, and in doing so also added the EXT3 patch 2.4-0.9.10-2410. Everything seems to work great, however I have been able to reproduce a crash over and over again. Here it is: #!/bin/sh mke2fs -j /dev/hda2 mount /dev/hda2 /mnt About 75% of the time, mount will result in a kernel Oops, the crash seems to be about something in

An EXT3 filesystem technically isn't supposed to require an fsck, correct? Well, as per my last email re: EXT3 Crash?! I ran an fsck on a couple of my LVMs. It said they were clean, but then I decided to be 100% sure and force an fsck. Error after Error after Error after Error. I wound up losing almost half the data on my LVM due to all the errors. What's the real deal? Am I doing

I’m digging through a build failure [1], and it looks like the loop idiom recognizer adds some instructions [2], and then removes them again [3]. I don’t understand why yet, but the LegacyPassManager detects that the structural hash of the function has changed, and complains that the pass didn’t correctly report that it changed the function [4] (even though materially, it didn’t). This raises a

Hi, With kernel 2.4.10, when I do $ mkdir foo; cd foo; rmdir ../foo; ls then ls becomes zombie. $ ps xau|grep ls liu 596 0.0 0.0 148 88 ? D 12:03 0:00 ls This does not happen with 2.4.10 on an ext2 filesystem, nor with 2.4.9/ext3. The command cd instead of ls is OK. Distribution is Slackware 8.0 and the kernels are stock ones. 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

I have rebuilt my kernel 2.4.10 for ext3, converted all my partitions and hard coded them in my fstab to ext3. when I type "df -t ext2", none of my partitions show up. when I type "df -t ext3", all my partitions show up. Everything seems to work fine. except upon a recovery...my system runs fsck and seems to do a ext2 recovery, which takes some 15-20 minutes. any ideas?

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

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, I am a new ext3 user and I am having problems similar to what many people are facing on this list. I have done everything as the emails suggest. I am using SuSE 7.3 with the the 2.4.10 kernel and ext3 compiled as a module. Because it is 2.4.10 kernel, I created all my journals from a rescue disk and everything seems to be working right for the non-root filesystems. My fstab has all my