similar to: some benchmarks

On Tue, 24 Jun 2003 ext3-users-request@redhat.com wrote : >Send Ext3-users mailing list submissions to > ext3-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request@redhat.com > >You can reach the person

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

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

Wow, it takes a really long time to make a 2TB ext2fs. Are there better-than-default options that could be used for a large filesystem? mke2fs 1.34 (25-Jul-2003) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244203520 inodes, 488382016 blocks 24419100 blocks (5.00%) reserved for the super user First data block=0 14905 block groups 32768 blocks per group,

Hello, I am trying to set up some Cisco 7940G phones with the 3com POE injectors. I have the 3CNJPSE24 power injector, this is the rackmountable 24 port injector. My question is does anyone know how to serial console into these things? I have tried just about every cable setup I can think of and baud rates but I can't seem to get anything out of it. I want to check to see what certain

Hi, can anyone recommend a Linux based TFTP server to go on an asterisk box? Thanks in advance Robb

That was a good hint! Yes, I've installed SP2, and it realy seems to be the Problem. Now I've checked that on a machine with SP1 - and the jobs from the same printqueue are removed correctly there! -------- Original Message -------- Subject: Re: [Samba] Samba 3.0.9 doesn't remove printjobs ? (14-Dez-2004 19:13) From: novosirj@umdnj.edu To: t.pompe@architekt-prinz.at >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, after upgrading to samba 3.0.8 (debian/unstable, i386) i too encounter similar problems as reported here: http://lists.samba.org/archive/samba/2004-November/095567.html upon logoff from a win2k(sp4) client, the profile cannot be saved and the samba logfile from the client (prinz) gives: [2004/11/26 17:57:06, 2]

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

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

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?

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

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

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

While I untar a large archive on xfs , ext3 (ver 1.3 and ver 1.4) file systems , on ppc processor and kernel ver 2.6.21 , I get an error. Also sometimes, on ext3 (1.3 and 1.4) the file system goes read-only while untarring. The same tar file when untarred on a i386 machine works properly. ERROR: -------------- tar: Skipping to next header gzip: stdin: invalid compressed data--crc error tar:

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

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

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

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