similar to: htree in 2.4.23

I've backported all of the bugfixes to the 2.5 dxdir/htree patches to 2.4, and have created a new set of patches for Linux 2.4.21rc5. At this point it *looks* like we've fixed all of the htree bugs that people have reported, including the brelse bug, the memory leak bugs, and the NFS compatibility problems. I've done *very* light testing, and things seem to work, but I'm now

There's a new set of ext2/3 patches for 2.4.21-pre5 available at: http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21pre5-2 and in broken out form at: http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21pre5-2 New to this patch set include: * A kludge to help htree work well with Linux's NFS implementation * Allow the orlov allocator to be disabled via a

Guys, I have recently applied the latest 2.4 htree patch on a heavily loaded nfs server. The nfs server serves around four very busy clients that deliver email in maildir format and pop3/imap clients. Being maildir I presumed that the htree patch would improve performance - but I was wrong. Load on the server went up by around 25-40%. After 3-4 hours of heavy use the clients load went up to

Hi Ryan, >> This is a completely fresh loopback EXT3 filesystem, untouched by fsck -D, >> and normally unmounted. > Oh, and I've attached the current version of my test program if anyone is > interested. > ... > It can corrupt my loopback test filesystems in under 5 minutes. Note that it > will completely destroy any data in its working directory, however. I am

Just out of curiosity: Is htree in 2.6.0-test11 ? -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916 Referat V a - Kommunikationsnetze - AIM. ralfpostfix

Hello, Could someone create some newer htree patches for the 2.4.x kernel? There are some bug fixes in the 2.4.21-rc releases that would be nice to have but the htree patches preceed those and they won't apply cleanly to later pre/rc kernels. It sounds like Marcelo may be about ready to put out 2.4.21 so it may just be worth holding off until that happens, but I don't suspect much will

Hi there, : without index mount: root@codeman:[/test] # time randfiles foo 20000 real 1m10.501s user 0m0.240s sys 1m8.590s root@codeman:[/test] # time randfiles foo 100000 real 32m55.929s user 0m1.890s sys 32m2.500s : with index mount: root@codeman:[/test] # time randfiles foo 20000 real 1m8.428s user 0m0.350s sys 1m6.780s root@codeman:[/test] # time randfiles

Apologies for the newbie question: I have a (stock) 2.4.20 build (*not* -ac), and I'm trying to work with large ext3 directories. By large, I mean 160,000 files per directory. (Yes, I know it would be better in nested directories but such is life). I feel htree would benefit me. Having upgraded from an earlier version of 2.4, I don't see any change, and close reading of the 2.4 changelog

Hi Guys, I am running ext3 on kernel v2.6.5. I have an ext3 filesystem with dir_index and data=journal for /var/spool/exim Today I noticed in the exim logs a bunch of 'failed to unlink /var/spool/exim/input/P/1BRbSP-0006hy-Jp-D' I also noticed these in the kernel logs: EXT3-fs warning (device hda12): ext3_unlink: Deleting nonexistent file (612870), 0 EXT3-fs warning (device hda12):

Hi all, I've pushed my current set of ext3 diffs (against Marcelo's current tree) to http://people.redhat.com/sct/patches/ext3-2.4/dev-20030314/ This includes: 00-merged/ diffs recently merged into 2.4 10-core-fixes-other/ misc fixes/tweaks from akpm, adilger 11-core-fixes-sct/ misc fixes/tweaks from sct 20-tytso-updates/ Ted's recent updates 21-updates-sct/ recent sct diffs

Hi Guys, I am planning on upgrading an existing NFS exported filesystem to the ext3 htree patch on kernel v2.4.23. Will the patch index directories automatically after tune2fs -O dir_index or should I do an e2fsck -Dfy on the filesystem before remounting?

Hi Guys, I am quite keen to try out the new htree extensions to ext3 however I wish to use them under NFS. I have noticed comments from the developers saying that it doesn't work properly under NFS. What exactly is the current status of the issue?

Hi, Just thought I'd share some test results of mine in case anyone is interested. Basically the tests are siumulating what our product does with files - although the tests do it a lot quicker (not as many files though). The test is to create 1 million files (each containing the text of the file number) spread over a number of directories. The files are then removed in the same manner as

I decided that I would try out 2.5.44, and I noticed that htree was merged. If I don't do the tune2fs -O dir_index, and e2fsck -D, the (exisintg) fs won't use htree, right? Once I do the tune2fs and e2fsck, will I still be able to go back to a non-htree kernel if needed? (Will a htree-ized fs work on a non-htree kernel?) I'm guessing that it won't. I've seen a 2.4 htree

Over the last two days we've been seeing a fair bit of this: ---- # ls -laR > /dev/null ... ls: ./server2/b/user/bxyz/392.: Input/output error ---- This is with the latest htree patches applied to 2.4.19, and latest e2fsprogs-test, on a dual AMD system, with 5x73GB SCSI drives on a MegaRAID controller. We're using the gcc 2.96 that comes with RH7.3. esfsck shows "Inodes that

Apologies for the newbie question: I have a (stock) 2.4.20 build (*not* -ac), and I'm trying to work with large ext3 directories. By large, I mean 160,000 files per directory. (Yes, I know it would be better in nested directories but such is life). I feel htree would benefit me. Close reading of the 2.4 changelog suggests that htree isn't in there - only a patch to prevent non-htree

Well here is what I got from testing htree with NFS. http://labs.zianet.com/benchmarks_html/postmark_benchmarks_NFS_100_htree.html It looks like htree improves performance when the storage device is local(as per my previous post) but it looks like htree degrades performance when used in conjunction with NFS. I am going to try it with gigabit ethernet when I get the time to see if maybe I am

Hi Ryan, > I am running your program now over an hour without any corruption on the > loopback mounted ext3 filesystem. shit, I thought testing over an hour (10mins your program, umount, fsck -fD test.img in a loop) is enough but it isn't. Damn f*ck :( root@codeman:[/] # fsck -fD test.img fsck 1.29 (24-Sep-2002) e2fsck 1.29 (24-Sep-2002) Truncating orphaned inode 6871 (uid=0, gid=0,

I post a patch for comment on ext2-devel for the NFS cookie bug. Did not get any feedback yet. As Ted suggested, it set the cookie to -1 on EOF, even though it is not seek able to there. I only test it with Stephen's "readdir.c". Not have chance to run it on a NFS server yet. Do you have more information about the cache trashing bug? Regards, Chris ===== dir.c 1.5 vs edited

hi, i have a tricky situation here and and don't know where to start with the solution. i happened to set up a linux system, but i had to install the base system on another machine. i used e2fsprogs 1.30-WIP (30-Sep-2002) for this. now the machine is up and running, but i have to use e2fsprogs 1.27 (8-Mar-2002). it's a debian system and i wanted to stay sane & stable, hence using