similar to: EXT3 and large directories

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

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

Hello, How to upgrade existing ext3 partition to new features? Moved from RHEL3 to RHEL4. I had to install from c0d0p6 so partition could not be reformated during install. Thanks, Mindaugas # dumpe2fs /dev/cciss/c0d0p1 | fgrep features dumpe2fs 1.35 (28-Feb-2004) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super # dumpe2fs

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, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works

Hi, I've run many time e2fsck, but in a special dir ls tells me: ls: r?cksendung-wlan.dvi: No such file or directory ls: baf?g_r?ckmeldung.latex: No such file or directory ls: finpr?f.pdf: No such file or directory $ cat finpr?f.pdf cat: finpr?f.pdf: Datei oder Verzeichnis nicht gefunden I don't know what to do? How can I find the failure? If I cat the files with debugfs, I see the

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 am running into performance issues with ext3. Historically we had our image files (pictures of cars, currently 5.3 million) sub divided into a directory structure [0-9]/[0-9]/[0-9]/[0-9], where we would take the first 4 letters/numbers of the file name and use that to put it into this structure. Letters [a-cA-C] would become a 0, [d-fD-F] a 1, etc. As the file names used to be based on VIN

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, I have 2 boxes with 1.5TB storage with ext3 fs, and the kernel is 2.6.11.8. I'm using E2fsprogs 1.37 for FS creation. And, Filesystem revision #: 1 (dynamic) There are 2 scenarios: 1. All SATA drives, RAID5 2. All PATA drives, RAID5 and wrapped in log volumes. I'm having lots of issues with fsck. I did search, but somehow not getting the right information. needs_recovery

Hi, Fedora Core ext3 file systems newbie questions: Just interested in the Linux ext3 features but got confused with "large_file" and "ext_attr". First, what's the "large_file" feature REALLY means? For file systems created with same commands and options some file systems have it on while some not. It is said that the feature is automatic -- If there is a

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

Peter Kjellstr?m wrote: > On Monday 23 January 2006 16:46, Plant, Dean wrote: >> I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to >> performance problems with Arkeia Network Backup and AIT-4 tape >> drives. The backup database is stored on a v4.2 created ext3 >> partition. When accessing this partition after the downgrade, Centos >> complains on

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

I hope this is the right list. I have created an ext2 filesystem and removed the dir_index feature. I don't know if this kind of experimentation is going to help me learn something about filesystems or not. Well what is dir_index? Then I ran e2fsck -f -v -pD and the /dev file. Now what did I remove? Htree. I guess it can always be put back and it's on an experimental filesystem.

Hi, I've installed a few Fedora Core 4 and Fedora Core 5 recently, and found that the new ext3 file systems created with new mkfs.ext3(1.38+) has one more field than EXT3 created with old mkfs.ext3(1.34-), even the latter's dir_index feature was turned on and file systems were upgraded with "e2fsck -y -f -D" command. I have three questions thereafter: 1) what does the

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

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

Hi, I have two 3TB (hardware RAID-5) ext3 filesystems and recently added 1TB to each. I resized each filesystem and e2fsck -f reports that both are fine. However, when I look at the ext3 parameters with tune2fs -l one seems to have some parameters that the other one doesn't. In particular, one has: "Reserved GDT blocks", "Filesystem created", "Default directory

Is there a document anywhere offering guidance on the optimum use of ext3 filesystems? Googling shows nothing useful and the Linux ext3 FAQ is not very forthcoming. I'm particularly interested in: 1. The effect on performance of large numbers of (generally) small files One of my ext3 filesystems has 750K files on a 36GB disk, and backup with tar takes forever. Even 'find /fs -type