similar to: dst cache overflow in 2.6.8

Hello, This is a CentOS 5.2 box configured as a router for a network handling about 200-300 Mbps, routing traffic to/from the internet for about 6,000 IPs. After about 2-3 days, the kernel complains about "dst cache overflow" and even thought it hasn't crashed, the network is un-responsive. All IP forwarding stops and the server cannot be reached from any network interfaces.

Yes, the clients are doing lots of creates. But my question is, if this is a memory leak, why does ocfs2 eat up the memory as soon as the clients start accessing the filesystem. Within about 5-10 minutes all physical RAM is consumed but then the memory consumption stops. It does not go into swap. Do you happen to know what version of ocfs2 has the fix? If it was a leak would the process not be

Hi, I have a centos 5.6 xen vps which loses network connectivity once in a while with following error. ========================================= -bash-3.2# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available

Hi, I have a centos 5.6 xen vps which loses network connectivity once in a while with following error. ========================================= -bash-3.2# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available

Hello. I''m running Xen 3.0.1 on the following hardware: Dell SC1425 Rack Server 1x Intel Xeon 2.8GHz (64bit on 32bit OS/Xen) Hyper-threading enabled 2GB memory 80+250GB SATA hard drives (sda, sdb) Debian Sarge on dom0. Different Debian versions on virtual servers. This is running as a virtualized web server. It''s hosting four virtual servers. 256MB memory is reserved to dom0

hi folks, i already posted this to the kernel mailing list a few days ago but nobody there seems to be interested in what i found out. since i believe this is a serious bug, i'm posting my perception again... the bug is about the handling of bad inodes in at least the 2.4.16, .17, .18-pre9 and .9 kernel releases (i suspect all 2.4 kernels are affected) and causes the names_cache to get

Hello! I am writing a FS filter that will be above the ext3 filesystem. For my own purposes I need severl bytes in inode. There are not enough space current inode so I need to create my own inode functions alloc_inode() & destroy_inode(). The problem causes when destroying slab cache at removing my module (rmmod). kmem_cache_destroy: Can't free all objects What I do: - install my

On 07/27/2018 08:10 AM, Bowie Bailey wrote: > The problem is that I can't find 2.4G of usage. Are your results from "top" similar to: ? ps axu | sort -nr -k +6 If you don't see 2.4G of use from applications, maybe the kernel is using a lot of memory.? Check /proc/slabinfo.? You can simplify its content to bytes per object type and a total: ? grep -v ^# /proc/slabinfo

On 7/27/2018 12:13 PM, Gordon Messmer wrote: > On 07/27/2018 08:10 AM, Bowie Bailey wrote: >> The problem is that I can't find 2.4G of usage. > > > Are your results from "top" similar to: > > ? ps axu | sort -nr -k +6 That looks the same. > > If you don't see 2.4G of use from applications, maybe the kernel is > using a lot of memory.? Check

I have just completed the installation of a new firewall running Shorewall 1.4 on Mandrake 9.2 for our campus network. It appears to be running fairly well so far, but is generating significantly more log entries than our previous linux 2.0.x firewall... Our previous firewall enjoyed more than 6 years of 24/7 operation with no downtime before we finally decided it needed more horsepower, and

> From: Nico Kadel-Garcia <nkadel@gmail.com> > Date: December 28, 2006 6:32:42 AM EST (CA) > To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> > Cc: "Bhatia, Nikhil" <bhatia@ornl.gov>, xen- > devel@lists.xensource.com, xen-users@lists.xensource.com, > ian.pratt@cl.cam.ac.uk > Subject: Re: [Xen-users] RE: [Xen-devel] Xen-3.0.3 migration problems > >

Rafael, You seems to be the person who added --start-lib and --end-lib to gold (*1), so I think you are the best person to ask about it. :) What is the intended use case of the options? Do you think we should support that in LLD? If we want to support that, then I think we can think of two implementation strategies: - Link object files between --start-lib and --end-lib normally and garbage

Hi, I regularly have errors (kernel: dst cache overflow) and crash of a firewall under Linux 2.6.17 and the route patch from Julian Anastasov. With rtstat I see that the route cache size increases regularly without never decreasing. I have this parameters: fw:/proc/sys/net/ipv4/route# grep . * error_burst:1250 error_cost:250 gc_elasticity:15 gc_interval:60 gc_min_interval:0

> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: >> I have seen this error in many postings, but the solutions seem not to >> apply in this case. This error happens during a small file transfer >> (gif image) and after 75% of a 165G rsync job (the building file list >> portion is complete.) Most solutions I saw were related to not having >>

What happens to the block layer if the block request queue gets very, very long? Imagine there are many DomUs and they are all working against VERY SLOW disks. I wish I understood the entire chain better, and I''m sorry to ask such a vague question. I understand this is a weird question, because the performance implications of this scenario are horrific. The reason I ask is that

Starting with 3.7 rc1, my workstation seems to loose ram. Up until (and including) 3.6, used-(buffers+cached) was roughly the same as sum(rss) (taking shared into account). Now there is an approx 6G gap. When the box first starts, it is clearly less swappy than with <= 3.6; I can''t tell whether that is related. The reduced swappiness persists. It seems to get worse when I update

Hi Guys, My users are reporting some issues with memory on our lustre 1.8.1 clients. It looks like when they submit a single job at a time the run time was about 4.5 minutes. However, when they ran multiple jobs (10 or less) on a client with 192GB of memory on a single node the run time for each job was exceeding 3-4X the run time for the single process. They also noticed that the swap space

The patch below makes some needlessly global functions static. diffstat output: fs/smbfs/inode.c | 2 +- fs/smbfs/proc.c | 6 +++--- fs/smbfs/proto.h | 5 ----- fs/smbfs/request.c | 6 ++++-- 4 files changed, 8 insertions(+), 11 deletions(-) Signed-off-by: Adrian Bunk <bunk@stusta.de> --- linux-2.6.10-mm1-full/fs/smbfs/proto.h.old 2005-01-04 00:57:42.000000000 +0100

https://bugzilla.netfilter.org/show_bug.cgi?id=823 Summary: IPv6 NAT memory leaking Product: netfilter/iptables Version: unspecified Platform: x86_64 OS/Version: other Status: NEW Severity: critical Priority: P5 Component: ip6_tables (kernel) AssignedTo: netfilter-buglog at lists.netfilter.org

Hello, I work in a hosting company, we have tens of Xen dom0 running just fine, but unfortunately we do have a few that get out of control. Reported behaviour : - dom0 uses more and more memory - no process can be found using that memory - at some point, oom killer kicks in, and kills everything, until even ssh the box becomes hard - when there is really no more process to kill, it crashes