similar to: ext2/ext3 directory handling

Hi all, Fewer days ago a CentOS box server suffered a manual and unexpected reset (too large to explain: there are silly people in everywhere). The result was the system did not mount de root (/) partition and the boot process was stopped. I repair it easily: boot from LiveCD (Knoppix in my case), umount root partition and pass the e2fsck utility. Because of that I've used several fs tools

Hi, first of all, apologies if this isn't the right mailing list but it was the best I could find. If you know a better mailing list, please tell me. Today I tried to defrag one of my filesystems. It's a 3.5T large filesystem that has 6 software-raids in the bottom and then merged together using lvm. I was running ext3 but removed the journal flag with thor:~# tune2fs -O ^has_journal

I have made some more research and found out the following .. thor:~# df -i Filesystem Inodes IUsed IFree IUse% Mounted on -[cut]- /dev/mapper/vgraid-data 475987968 227652 475760316 1% /data thor:~# strace e2defrag -r /dev/vgraid/data -[cut]- mmap2(NULL, 1903955968, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x46512000 (delay 15 seconds

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.

Hello everybody, reading about the speed improvements possible with (on boot) preloaded files (which should be continuous on disk) I searched for a ext3 defrag program. I found an ext2 defrag program (http://www.ibiblio.org/pub/Linux/system/filesystems/defrag-0.70.tar.gz, available in debian as defrag) which would have an optimal feature (moving files by a list) but refuses to work on ext3.

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

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

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?

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

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

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, I'm working with Prof. Zadok on versionfs, a stackable versioning file system. I face some problems with the unlink operation on ext3 with htree. On an unlink, I make a copy of the file (version/backup) and unlink the original file. But some files that have been unlinked are "linked back" to another file. For example, on deleting the file 'foo', the file itself is

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

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

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

If you are using XFS - there is mount option "discard|nodiscard" From XFS man page: discard|nodiscard Enable/disable the issuing of commands to let the block device reclaim space freed by the filesystem. This is useful for SSD devices, thinly provisioned LUNs and virtual machine images, but may have a performance impact. Note: It is currently

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