similar to: ext3+quota+load: deadlock

hi, Can I use quota with ext3 on a loaded system without experimenting deadlocks nowadays? I'm using rh7.3 kernel 2.4.18-19.7.x thanks -- Juan Pablo Abuyeres <jpabuyer@tecnoera.com>

Good evening. We have some heavy-loaded servers on ext2, and we want to migrate to ext3fs. But we need full and stable quota support. I have headrd that there are some problems in quota usage under ext3fs. Is it true? Should we decline the ext3 usage as impossible in our servers? We need high-level stability in our server (hosting). Thanks before. -- Best regards,

hi guys, I have an asterisk server and a mediatrix 1204 gateway. I make calls through the mediatrix unit (only outgoing calls). The problem is, every call I make through the mediatrix unit is logged in the cdr as 'ANSWERED', even if the call was 'NO ANSWER' in practice. Any ideas how to make cdr records accurate? Thanks! -------------- next part -------------- An HTML

hi, I was trying to use ext3 with quota and 2.4.18, but when the system had sustained load, eventually the system fell on deadlock. By that time, I was told to use the latest -ac patch, and maybe the problem would no longer exist. But instead I went back to ext2 and waited for 2.4.19 to come out. Now I tryed 2.4.19 with ext3 and all the same thing, but the system hanged up again. Please tell

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,

HPA, I believe that support to boot windows CD bootsectors was broken in 3.05. I have tested 2.13, 3.00, 3.02, 3.05, 3.06, 3.08, 3.11, and 3.20pre6. All versions >= 3.05 are broken. All versions <= 3.02 work fine with the same config. The error message I get is: ================================================================ IOSLINUX 3.20 3.20-pre6 Copyright (C) 1994-2005 H. Peter Anvin

HOPEFULLY fixes the 3.05 initrd bug. Please try it out and confirm; I will try to release it as 3.06 tomorrow. SIGH... -hpa

Hi all, My system is : kernel 2.4.8 with ext3-0.9.6 patch e2fsprogs-1.22-2, mount-2.11g, util-linux-2.11f And ext3 filesystem works fine, but when a vfat partition is mounted: [fargo] [~] # mount /dev/hdd1 /mnt/tmp [fargo] [~] # mount /dev/hda1 on / type ext2 (rw) none on /proc type proc (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/hdd1 on /mnt/tmp type vfat (rw) everything looks

Hello ext3-users, We have a RH71 machine running 2.4.16 kernel with e2fsprogs 1.25. I noticed many of these errors in our logs. EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #884828: directory entry across blocks - offset=0, inode=404600689, rec_len=23080, name_len=59 EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #966714: rec_len % 4 != 0 -

An ext3 update which also applies to linux-2.4.16 is available at http://www.zip.com.au/~akpm/linux/ext3/ Quite a lot of miscellany here. It would be appreciated if interested parties could please test it in preparation for sending upstream. Thanks. Changelog: - Merged several ext2 sync-up patches from Christoph Hellwig - Drop the big kernel lock across the call to block_prepare_write.

Hello, I search through but I didn't find a clear answer about it. I have a rh 6.2 based box where I made many steps of upgrades. Some of them, not being available the binary rpm glibc 2.1 based, I obtained using src.rpm from rh 7.2 and then runnig #rpm --rebuild package.src.rpm and then installing the generated binary: great sw rpm!!! My rpm version is 4.0.2-6x for both rpm, rpm-devel,

Hi all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

Hi all, When I ran the experiments to compare an application''s execution time in both a domU (named cctest1) and a native Linux machine (named ccn10), I noticed the application executes faster in domU. The host of the domU (named ccn9) and ccn10 are two nodes of a cluster and they have same hardware configurations. domU (cctest1) is created by exporting loopback files from dom0 on

I have kernel 2.4.16 with ext3 compiled (not as a module), with redhat 7.1, and downloaded lilo 22.1 from util-linux 2.11n but still, on init the root fs is mounted initially as ext2 as read-only, afterwards it is unmounted and mounted again as read-write ext3. this causes problems upon unclean shutdown where I have to fsck it just like ext2. does anyone know this problem ?

We are looking to set up a cluster of machines using LVS and running EXT3 on each machine. Does anyone have any feedback on doing this? Any known gotchas? The stable version of IPVS kernel module is for 2.4.12. The latest stable kernel in 2.4.16 The latest patch for ext3 is for 2.4.14 or 2.4.17pre2. Any suggestions on what combo to try? Thanks, Charlie

Everyone, We just had a pretty bad crash on one of production boxes and the ext2 filesystem on the data partition of our box had some major filesystem corruption. Needless to say, I am now looking into converting the filesystem to ext3 and I have some questions regarding ext3 and Linux software RAID. I have read that previously there were some issues running ext3 on a software raid device

Hello, Two lapply questions (system info and sample data below): 1) Why does the first form of command1 add the name of y _after_ the str() output rather than before as does the second (preferred) form? # command1 version1 invisible(lapply(ls(pattern='bn'), function(y) cat(y, "\n", str(get(y)), "\n") )) # command1 version2 (preferred output)

Hi. I'm using Debian. Is this a Redhat-only list, or is it only hosted by RedHat? I recently changed my filing systems over to ext3, but deliberately left the forced boot check parameters alone so my system checks after 20 mounts. I notice that the fsck takes a good ten times longer than under ext2, to perform the cleanly unmounted check. (On the occasion where I did unmount dirtily, the

Hi. I'm just trying to install a TE410P card (jumped as E1). But I'm having problems loading the kernel module. [root@asterisk1 src]# modprobe wct4xxp /lib/modules/2.4.21-32.0.1.ELsmp/misc/wct4xxp.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the

Okay, let's hope *fourth* time is a charm... Changes in 3.06: * Fix typo that caused the ramdisk to load in the wrong place. Changes in 3.05: * New API function "shuffle and boot"; allows COM32 modules to load or construct (almost) arbitrarily complex objects, e.g. a kernel and its initrd/initramfs in pieces, and have the API core