similar to: ext3 tree size

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

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

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

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

I have an ext3 filesystem that has several directories and each directory gets a large number of files inserted and then deleted over time. The filesystem is basically used as a temp store before files are processed. The issue is over time the directory scans get extremely slow even if the directories are empty. I have noticed the directories can range in size from 4k - 100M even when they are

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

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

This may or may not be ext3 related but I am trying to find any pointers which might help me. I got a number of HP Proliant DL380 g5 with a P400 controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64. Every time during reboot these systems panic after the last umount and I believe before the cciss driver is getting unloaded. The last messages I am able to see are: md: stopping

Hi Guys, I have experienced a recent performance issue with an ext2 filesystem. Essentially I have had several files that get overwritten on average once per day. This has been happening for about a hear when the program accessing and reading those files started from several milliseconds to 15-20 seconds to open and read the file. Moving the directory to a new name and copying the contents

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Searching in the ext3 filesystem mailing list I have seen that there is an indexed directory extension for it. Is this extension stable code ? Has anyone test it ? How may I obtain and install it ? Is it available in any of the last kernel releases ? Greetings. - --- Carles Xavier Munyoz Baldó carles@descom.es Descom Consulting Telf: +34

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

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

Hi, I enabled dir_index on a filesystem and dumpe2fs -h also reports this. My understanding is that this will be used for newly created directories and that old directories can be indexed using "fsck.ext2 -D". Two questions: - Is there a way to tell is a given directory is indexed or not? - Is there a better way to index the root fs than to boot off a live CD? Best, Norbert

With the help of Jan Iven I have been able to compile openssh-2.9.9p2 on Solaris 2.6 with AFS/kerb4 support using gcc. ./configure --sysconfdir=/etc/ssh --with-tcp-wrappers \ --with-egd-pool=/var/run/egd-pool \ --with-kerberos4=/usr/athena --with-afs=/usr/afsws to do this I modified the resulting Makefile, from: CPPFLAGS=-I. -I$(srcdir) -I/usr/local/ssl/include

Hi, I just tried the 2.6.22-r1 candidate to test whether some bug I have hit in the past still exists. I did use 2.6.20.6 so far. So, I have cleanly rebooted to use the new kernel, after the machine came up I tried to mess with the bug, and had to reboot again to play with kernel commandline parameters. Unfortunately, on the next reboot fsck was schedules on my filesystem after 38 clean

I've been thinking recently that we should re-enable DIR_INDEX in mke2fs by default. When it first came out, we had done this and were bitten by a few bugs in the code. However, this code has been in heavy use for several thousand filesystem years in Lustre, if not elsewhere, and I'm inclined to think it is pretty safe these days. Likewise, RHEL/FC have had RESIZE_INODE as a standard

Hello, I am using kernel version 2.4.7-10 I upgraded one of the ext2 partition to ext3. the partitions are nearly empty. I ran a program to create empty files, having names in lexicographical order. The time taken to create empty files (100 .. 100000) is same on an ext2 partition and a ext3 partition. Can anyone pls. tell me why there is no difference in the time taken. Is the htree algo.

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

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?

I have just been thru rebuilding a server that had been suffering severe performance problems. I transferred the partitions to another hard drive, copying into freshly formatted filesystems. This made a HUGE difference in performance. One key directory structure stores email messages in an structure where there is a directory for each mail account, and the messages are stored in