similar to: Fedora Core 4 and FC5's NEW EXT3 file system: "Reserved GDT blocks" ???

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

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

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

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

* "Bill Cunningham" <billcun@suddenlink.net> hat geschrieben: > 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 >

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

i posted on rhel list about proper creating of 6tb ext3 filesystem and tuning here.......http://www.redhat.com/archives/nahant-list/2006-November/msg00239.html i am reading lots of ext3 links like...... http://www.redhat.com/support/wpapers/redhat/ext3/ http://lists.centos.org/pipermail/centos/2005-September/052533.html http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ............but

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.

On 8/17/14, 12:28 PM, Roland Olbricht wrote: > Hello everybody, > > first of all thank you the development of Ext2/3/4. It works like a > charm and makes it possible to base applications on it. > However, "df" says: > > Filesystem 1K-blocks Used Available Use% Mounted on > ... > /dev/sdc 468346644 409888536 35015532 93% /opt/ssd >

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11,

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 made a filesystem (mke2fs -j) on a logical volume under kernel 2.6.20 on a 64-bit based system, and when I try to mount it, ext3 complains with EXT3-fs: dm-1: couldn't mount because of unsupported optional features (80). I first thought I just forgot to make the filesystem, so I remade it and the error is still present. I ran fsck on this freshly made filesystem, and it completed with

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

Hello Eric, thank you for the quick reply and the explanations. > dumpe2fs -h output might show us that. Filesystem volume name: <none> Last mounted on: /opt/ssd Filesystem UUID: 75d6aae6-1746-4260-994b-148dfdb5af95 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype

Hi all, I issued the commands on a single disk system: with two partitions / is linux sda1 and /home is sda3 yum -y update yum -y install e4fsprogs reboot umount /home tune2fs -O extents,uninit_bg,dir_index /dev/sda3 e2fsck -yfDC0 /dev/sda3 That worked just fine. I then had a different system that is software raid. where / is linux and md0 and /home is md1 yum -y update yum -y

Hello guys, I have some difficulties to understand what really are the numbers behing "df" and tune2fs. You'll find the output of tune2fs and df below, on which my maths are based. Here are my maths: A tune2fs on an ext3 FS tell me the FS size is 3284992 block large. It also tell me that the size of one block is 4096 (bytes if I'm not wrong?). So my maths tell me that the disk

Hello everybody, first of all thank you the development of Ext2/3/4. It works like a charm and makes it possible to base applications on it. However, now I have the first time where I need more information to understand the behaviour of a ext4 installation on a 480 GB harddisk. It holds a database with a size of 355 GB, as said by "du -m": ... 355263 /opt/ssd However,

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