similar to: Re: ARGS [PATCH] fix htree dir corrupt after fsck -fD

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

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 looking through the 2.4.20pre changelogs, I see there's been a bunch of Ext3 patches since 2.4.19. I'm keen to take advantage of any bug fixes and performance improvements, but am nervous about using 2.4.20 until it's completed its release cycle. Is there any way to get a patch just containing the Ext3 changes? Are there any changes since 2.4.20 that are very important, either

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

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

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

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

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

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

My reading of the kernel.src.rpm doesn't indicate that Severn has ext3 htree patches. Stephen, were there any issues seen during Cerberus testing ? Regards, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com

Hi, Someone knows if the htree patch is applied in the last kernel for RedHat 8 (kernel-2.4.20-18.8) for the ext2/ext3 filesystems ? Greetings. --- Carles Xavier Munyoz Baldó carles@unlimitedmail.org http://www.unlimitedmail.net/ ---

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

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?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Is there any home page for the htree for ext3 project ? Any place where I can follow the status of the project and download the last patch versions ? Greetings. - --- Carles Xavier Munyoz Baldó carles@descom.es Descom Consulting Telf: +34 965861024 Fax: +34 965861024 http://www.descom.es/ - --- -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Have *ALL* the filesystem corruption issues that plague(d?) HTREE on 2.4.x cleaned up for 2.6? I believe they have, but before I enable this feature again, I'd like to be sure. Thanks. - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 http://doug.hunley.homeip.net && http://www.linux-sxs.org A day without sunshine

I just booted 2.5-bk current as of last night with the below patch¹ (which was recently posted to ext3-users) that un-static-ifies a struct dx_frame in namei.c. I then did my best torture test for the brelse bug: starting gnus (3600+ nnmh folders² with a total of XXX messages; it does a readdir on each of those folders) while doing bk consistancy checks in 2.5 and/or 2.4 kernel trees. All

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

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