similar to: Implementing ext3

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 =

I run a decent amount of 3ware hardware, all under centos-4. There seems to be some sort of fundamental disagreement between ext3 and 3ware's hardware RAID5 mode that trashes write performance. As a representative example, one current setup is 2 9550SX-12 boards in hardware RAID5 mode (256KB stripe size) with a software RAID0 stripe on top (also 256KB chunks). bonnie++ results look

I am using a terabyte RAID5 with ext3 and created using mdadm, to store jpeg files on a rehdat 7.3 system. I need to write files to the RAID5 at the rate of 800 files per second, and each file is about 10-20 KB in size. I have tried using data-writeback and the noatime options while mounting, and I am also using a stipe-size of 4MB (since 4MB was the max that mdadm would allow me), and i have

Hello I try again. Can anybody of you acknowledge or not if mode data=journal in ext3 is safe to use in Linux kernel 2.6.x? Wee need to have a very consistent and integrity for our filesystem, and it would then be desired to journal both data and metadata. But if this mode can corrupt the filesystem as both Phil White and Nicolas Kowalski has experienced, it may be more advised to use mode

Hi, I recently upgraded one of my fileservers from 2.4.16 to 2.4.18 plus the ext3-cvs.patch that Andrew Morton pointed me to for addressing and assertion failure. Since then I have been getting lots of errors like: May 21 14:07:03 glass kernel: EXT3-fs error (device md(9,0)): ext3_add_entry: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927,

For some odd reason, I'm getting some off the wall occurances with a ext3 partition. During a normal reboot: /dev/sdb1 has reached maximal mount count, check forced. Is this normal? I thought JFS's were supposed to alleviate this check, or is that just for fs corruption? Here's my sys info: Linux 2.2.19 running Redhat 6.2 EXT3 is only on /dev/sdb1, mounted as /mnt/raid /dev/sdb1

On Sunday March 16, gilbertd@treblig.org wrote: > Hi, > I've just built an 800GB RAID5 array and built an ext3 file system > on it; on trying to copy data off the 200GB RAID it is replacing I'm > starting to see errors of the form: > > kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in > system zone - block = 140509185 > > and >

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

I remember that there used to be a problem with disk quotas on Ext3 and Raid5 on the 2.4.x kernel series. I am running 2.4.14 with Ext3 and Raid5 and am having problems with quotas and am wondering if I have something misconfigured or if this combination doesn't work yet. -- Daniel R. Bidwell | bidwell@andrews.edu Andrews University Information Technology Services If two always agree, one of

I have a raid5 array on my web server for which I am currently considering a move to ext3. I want to use an external journal to improve performance. Since the external journal would reside on a drive that is not participating in the raid array, I'm wondering what the behavior of an ext3 filesystem is should the device an external journal is on should fail. If it reverts to ext2

Hi, I just installed Redhat AS 2.1 on a a new machine with tons of RAID5 space. During the install, I created the partition/filesystem /largedisk with 550784264 blocks. After everything is installed and mounted, I get the following in a df: /dev/sda8 550784264 32828 522773144 1% /largedisk The avail + used != total, not even close. I realize that the 32828 is probably the

Hello everyone, I've just recently joined the ext3-users list. I spent much of the weekend browsing over list archives and other tidbits I could find on the net, regarding using an external journal, and running in data=journal mode. From what I have seen looking around at what other folks are doing, data=journal with an external journal may be able to help our problem here. If I

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

Hello. I'm looking for assistance or pointers for the following problem. OS: RHAS2.1 enterprise16 HW: HP proliant 2CPU 6GB RAM, internal RAID1 + RAID5(4 x 10K 72GB) When we run any kind of process (especially tar for some reason) that creates heavy disk activity the machine becomes Very Slow, (e.g. takes 30-45 seconds to get a reply from ls at the console, or a minute to log in.) I

Errors happy in the early hours of the Morning 4 or 5 AM. every time , many directories and files can't be accessed , message "I/O error " display, all partitions become read-only no data lost and no data can be wirted ,only redress is a reboot. Distribution: REDHAT version 4 X86_64 update 5 Server Platform : IBM X 366 RAID Controller : IBM ServerRAID 8i Disks : 4*73G SAS

Hi, I'm formatting a flash with ext3, but I need to move the journaling file (/.journal) in the flash to prevent it's corruption. In previous message I read that it's possible (https://www.redhat.com/archives/ext3-users/2004-March/msg00009.html), but I can't find any /.journal in my ext3 fs. How can move the journaling file in the flash without /.journal file?? Thanks

Forgive my novice question, but I am a new student of Linux working on presenting the ext3 journaling filesystem to my class. I seek any advice on how to visibly demonstrate (including a purposeful crash of a Linux box) the benefits of ext3 over ext2. I am not worthy to lick the bootstraps of this group, but I beg for any help! The problem I am having extends to even locating the .journal file

----- Forwarded message from Neil Brown <neilb@cse.unsw.edu.au> ----- On Wednesday September 19, mfedyk@matchmail.com wrote: > On Tue, Sep 18, 2001 at 09:08:32PM +1000, Neil Brown wrote: > > On Sunday September 16, mfedyk@matchmail.com wrote: > > > Hi, > > > > > > I'm trying to

I'm experiencing strange behavior from my ext3 RAID5 array and my Fedora Core 2 system. Before I go crazy varying all sorts of tuning parameters, I thought some list subscribers might provide me with useful advice. The problematic array is: 3x Promise Technology Ultra 100 TX2 PCI cards 6x Maxtor 250GB IDE drives (one drive per cable) RAID level 5, 128Kb chunk size, EXT3: "mkfs -t ext3

Hi! Is there a way to view ext3 filesystem's maintained journal (in a human-readable-format)? I ask, because i have had a server crash before and now i'm wondering if i might take a look at last things that my server did straight before crash. I guess clarifying log insertions might be lost before buffers were flushed to disk. Thx.