similar to: Rsync Memory Issues - Kernel 2.4.18 - Box Hangs

I am getting an odd situation when backing up a number of ext3 filesystems and was wondering if it could be caused by journalling. Over the space of a minute the load average will jump from 2 to over 40 and the system will be unresponsive for anywhere from 8 to 25 minutes. I am going to be trying a number of things, but was wondering if anyone could see the reason for the high load given the

(Sent to linux-raid, linux-kernel and ext3-users since I'm not sure what type of issue this is) I've got a test system here running Redhat 7.1 + stock 2.4.9 with these patches: http://www.fys.uio.no/~trondmy/src/2.4.9/linux-2.4.9-NFS_ALL.dif http://www.zip.com.au/~akpm/ext3-2.4-0.9.6-249.gz http://domsch.com/linux/aacraid/linux-2.4.9-aacraid-20010816.patch All three patches applied

Hi, I am a new ext3 user and I am having some problems. I seem to have introduced a memory leak after adding ext3 support to the kernel. I noticed when running top or viewing /proc/meminfo my free memory pool seems to be decreasing while my buffers are increasing (around the same rate). I am currently using a root partition and a /var partition. I have listed the ext3 boot messages below.

Do you know what can cause the smbd process to steal out the cpu usage (99%) and keep running like that for days? I have a Samba PDC 3.0.1pre3 running on top of RH9 2.4.20 kernel. Below is the current top report. Strangely, the PDC still responds in reasonable good response times to heavy network duty.traced the log.%machine name% and didn't find anything . I haven't tried to restart smb

Hi, This morning I had some failed calls. On the console (and in the log) I saw the error "Unable to allocate channel structure". Before I restarted the process, I checked it's memory usage in ps and glanced at my free memory in top. Asterisk was using a normal ammount of memory, about 40M. I don't think this was a system limit. This was running Asterisk v1.0.2. Below is

Hi list, Time to time, my asterisk goes down.Verifying with TOP, I see the swap memory of the computer get used totally but, I don't see what the process is using it. Hereis a copy wath I see doing top. Does somebody have an idea ? My asterisk version is ====>>> Asterisk CVS-HEAD-08/18/04-22:30:24 Thanks Angel. 08:49:19 up 5:23, 1 user, load average: 0.50, 0.70, 0.64 35

Hi, One of my pbx's seems to be having some new issues. crackling interference on the zap channels running through the channel bank, and I noticed that these happen when I hit an "irq miss" in zttool: Current Alarms: No alarms. Sync Source: Digium Wildcard T100P T1/PRI C IRQ Misses: 82695 Bipolar Viol: 0 Tx/Rx Levels: 0/8 3 Total/Conf/Act:

Hello everybody! As I wrote in my mail the previous week ("BUG: 2.4.19pre1 & journal_thread & open filehandles") I followed the problem a little bit further. Here's my patch; I beg the ext3-maintainers (Stephen, Andreas, Andrew) to have a look at it and submit it to Marcelo and Linux for inclusion. (2.4 is for now for me more important than 2.5). Patch ----- On every

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Background: Large NFS/mail server. Dual PIII/1GHZ. 4GB memory. Mylex AcceleRAID 352 RAID controller (uses DAC960 driver). Intel eepro100 network cards. RedHat 7.3 with all errata. Kernel-2.4.18-5smp. 2GB of memory is used by a RAM disk for mail queue. ext3 filesystems (switched to ext2 to see if that helps). one large (100GB data partition).

All, I am running into a situation in which one of my ext3 filesystems is getting hung during normal usage. There are three ext3 filesystems on a CompactFLASH. One is mounted as / and one as /tmp. In my test, I am copying a 100 MB file from /root to /tmp repeatedly. While doing this test, I eventually see the copying stop, and any attempts to access /tmp fail - if I even do ls /tmp the

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

Hello all, Saturday night, after a couple of shots of bourbon, I realized that I had an old PC sitting in the garage that I could use as an Asterisk gateway if I just blew the dust off it and reloaded it with a modern Linux distribution. In my characteristically impulsive manner, I grabbed it and started cleaning it up so that I could put it in my office without my wife having a fit. The

Hello list, I have a problem with an NFS server for my network. It has ran kernels 2.4.18-ac4 - 2.4.21-ac1, all with problems. The -ac patches are used to provide the new style quota support. The system seems to have gotten even less stable with the new kernel versions. This morning around 5 am, I got a page the system was unresponding to NFS requests. I ssh'd in, and found the loadavg

Hi All, We're currently trying to use samba in an embedded application, so we're working with samba 3.0.2a compiled for PPC. We have a test application which will basically write, then read back and compare data files on the disk. The problems we see occur when we try using just over 3500 small files (< 10k each). It seems that after about 200 or so iterations of this test, we start

I sent this report sometime ago to l-k and to the preempt-patch maintainer, but omitted to send a copy here, where some people could have clues about the problem - so here it is: ----- Forwarded message ----- To: linux-kernel@vger.kernel.org, Robert Love <rml@tech9.net> Subject: oops with 2.4.18 and preempt patch, on SMP + ext3 machine Coming back home tonight, I found my machine in a bad

Back again with another oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k

Hi all! I have recently installed samba-3.0.2a-1 on my RedHat 9.0, Kernel 2.4.20-8 box. The box has a 300GB RAID5 array, 4GB of memory, and dual 2.4Ghz P4 processors with hyper threading enabled. When I copy a massive amount of files (~50GB) to the Samba server from a Windows 2K client, somewhere during that process (seemingly around 2 hours into the copy each time), my Linux box COMPLETELY

Sir or Ma'am: I have recently installed samba-3.0.2a-1 on my RedHat 9.0, Kernel 2.4.20-8 box. The box has a 300GB RAID5 array, 4GB of memory, and dual 2.4Ghz P4 processors with hyper threading enabled. When I copy a massive amount of files (~50GB) to the Samba server from a Windows 2K client, somewhere during that process (seemingly around 2 hours into the copy each time), my Linux box

Hi all! I have recently installed samba-3.0.2a-1 on my RedHat 9.0, Kernel 2.4.20-8 box. The box has a 300GB RAID5 array, 4GB of memory, and dual 2.4Ghz P4 processors with hyper threading enabled. When I copy a massive amount of files (~50GB) to the Samba server from a Windows 2K client, somewhere during that process (seemingly around 2 hours into the copy each time), my Linux box COMPLETELY

Hi... I have a Dell Latitute with an ATA/ATAPI-5 T13 1321D and it would seem that my disk access is extremely slow. I have the latest updated kernel from RedHat 8.0 kernel 2.4.18-27.8.0. Somehow I think it is related to the UDMA stuff (shows my level of understanding). I have run hdparm and although I think I should at least udma level 5, I have at most udma2 listed. Is this a kernel