similar to: ext3 filesystem options and Gluster -

(please reply on-list, so everybody can comment/help) Matt, thanks for the details, but apart from mount-option tuning and dir_index (which you've already enabled), I dunno why ls(1) would take *hours* to stat ~1M files... out of curiosity: are you able to try a newer kernel? does it change anything? Christian. ---------- Forwarded message ---------- The dir_index was enabled during

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

I'm setting up a new fileserver. It has two RAID controllers, a PERC 3/DI providing mirrored system disks and a PERC 3/DC providing a 1TB RAID5 volume consisting of eight 144GB U160 drives. This will serve NFS, Samba and sftp clients for about 200 users. The logical drive was created with the following settings: RAID = 5 stripe size = 32kb write policy = wrback read policy =

Dear Mailinglist, this morning I had a very strange problem with my SuSE Groupware-Server SLOX 4.1. The webmail-access was very slow and even with thunderbird the access to my mailboxes was not okay. I rebooted the whole system, but the problem still was there. I thought, this may be a problem with cyrusd, but I realized, that the error was somewhere deeper in the system, maybe in the

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

Hello, I have some performance problems in a file server system. It is used as Samba and NFS file server. I have some ideas what might cause the problems, and I want to try step by step. First I have to learn more about these areas. First I have some questions about tuning/sizing the ext3 journal. The most extensive list I found on ext3 performance tuning is

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

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

All, I'm requesting comments from the expert readers of ext3-users on these notes for tuning ext3 for performance. Most helpful would be feedback pertinent to RHEL 5; as XFS isn't supported under Red Hat Enterprise Linux these items are an attempt to match XFS performance with ext3. These items were culled from a number of sources. Will they be effective for achieving the performance

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.

Today our server had seriuos problems, we had to reinitiate it and run fsck manually. Dou you think it's an ext3, kernel (vanilla 2.4.19) or hardware bug? The errors were (from syslog): -------------------------------- Oct 6 16:10:25 nou kernel: attempt to access beyond end of device Oct 6 16:10:25 nou kernel: 72:02: rw=0, want=230266240, limit=4882432 Oct 6 16:10:25 nou kernel: attempt

Hi all, I was trying to mount root-partition which is ext3 partition with noatime and ro option. I included "ro" in the kernel command line But for mounting it with "noatime" option when I searched for some solution I came across a patch http://lkml.org/lkml/2007/8/5/38 But after applying this patch and including option "noatime" in

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

----- Original Message ----- From: "Bodo Thiesen" <bothie@gmx.de> To: <ext3-users@redhat.com> Sent: Monday, August 25, 2014 8:15 PM Subject: Re: filesystem > Hello Bill. [snip] > You're trying to understand what exactly? From the user point of view, > dir_index just makes directory accesses on very big directories faster. > When creating a new file, or

Howdy, are any of the Gluster folks going to SC10 next week? Mike

Is anyone using Gluster with the Rocks cluster system? If so, do you know if there is a Roll for Gluster? Or, do you have any advice about things to do and things to avoid doing? We're considering using Gluster with Infiniband on our cluster and trying to learn whether other people have done this so we can perhaps learn from their experience. Thanks. .. Lana (lana.deere at gmail.com)

Hello, Does anyone have experience using a 3ware 9650SE series raid controller on CentOS 6.0? I am getting very sporadic throughput with moderately sized files (0.5-2GB) on ext3. I have tried most of the mount time tuning options: * noatime * trying different journal types * setting commit=120 - helped a little Even after these optimizations it doesn't seem like the raid array is working

I have a rather large box (2x8-core Xeon, 96GB RAM) where I have a couple of disk arrays connected on an Areca controller. I just added a new external array, 8 3TB drives in RAID5, and the testing I'm doing right now is on this array, but this seems to be a problem on this machine in general, on all file systems (even, possibly, NFS, but I'm not sure about that one yet). So, if I use

Oddly enough, the performance of a 3Ware 9550SX controller seems to have improved when switching from 64-bit to 32-bit CentOS 5. This is a RAID0 device with 8 x 500gig barracudas and the noatime and data=writeback tweaks to that device in /etc/fstab. It's also quite a bit better than results on the same machine using CentOS 4.4 (64-bit). This partition is used to store scratch data

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?