search for: slabinfo

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

...reate 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 module (insmod) - Mount filesystem - list the mountpoint with ls -i - cat /proc/slabinfo shows: my_ii_cache 1 7 512 1 1 1 - I make umnount - cat /proc/slabinfo shows: my_ii_cache 4 14 512 1 2 1 Where did 4 came from? I believe it should be 0. - Then I remove module (rmmod): when callong function kmem_cache_destroy() I...

...this error means that the routing cache filled up. The maximum size of the routing cache can be set by changing /proc/sys/net/ipv4/route/max_size. The default on my mandrake install is 32768. The current size of the routing cache can apparently be determined by "grep ip_dst_cache /proc/slabinfo". On my router this value is slowly, but constantly, trending upwards at all times. However, if I list the cache with "route -Cn", or "cat /proc/net/rt_cache", I see significantly fewer entries than what slabinfo reports. Two things have changed since the time when my...

I have a CentOS 7 server that is running out of memory and I can't figure out why. Running "free -h" gives me this: ????????????? total??????? used??????? free????? shared? buff/cache?? available Mem:?????????? 3.4G??????? 2.4G??????? 123M??????? 5.9M??????? 928M??????? 626M Swap:????????? 1.9G??????? 294M??????? 1.6G The problem is that I can't find 2.4G of usage.? If I look

...ls are affected) and causes the names_cache to get confused. however, it is actually not a bug in ext[23] but in vfs layer. you can easily reproduce this effect by making an inode bad using debugfs (or using a bad one if you have, of course) and open() it with the flag O_CREAT set. watching /proc/slabinfo will show you the weirdness. consider /tmp/bad is a bad inode: # cd /tmp # ls | grep bad bad # cat bad cat: bad: Input/output error # cat /proc/slabinfo | grep names names_cache 0 2 4096 0 2 1 : 2 333 2 0 0 # echo foo >bad sh: bad: Input/output error # cat /proc/slabinfo | grep names names_cach...

I had the dom0 which unfortunately didn''t have a console on it hit a race condition and saw oom errors on it also. This happened after it was running for over 36 hours with a domU whose load average was avg was around 3 most of the time. changeset: 7396:9b51e7637676 Dom0 - UP i686, Centos 4.1, 768 megs domU-1 92 megs snmpd domU-2 92 megs snmpdd domU-3 410 megs postgres, tomcat 5.5,

...what version of ocfs2 has the fix? If it was a leak would the process not be more gradual and continuous? It would continue to eat into swap no? And if it was a leak would the ram be freed when ocfs was unmounted? Is there a command that shows what is using the kernel memory? Here is what /proc/slabinfo shows (cut down for formatting). I don't understand how to read this so maybe someone can indicate if something looks wrong? ======= # cat /proc/slabinfo # name <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> nfsd4_delegations 0...

...ch log as i thought could be helpful in attachments. Host bk - about to get a reboot, as xend already got killed Host sw - 800MB/2GB used for nothing, Attachments contains : - memory graph (by munin) - it might help to see the pattern of memory usage cat from : - grub.cfg - /proc/meminfo - /proc/slabinfo - /proc/vmstat - /var/log/kern.log - /var/log/xen/xend.log Result from : - dmesg - dpkg -l - free - lsmod - top - vmstat - xm info - xm info -c I''d appreciate any feedback about such behaviour, and would be happy to provide additional information. Those are productions servers, the onl...

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

...s into its own directory under /sys/fs/cgroup/openrc. But top(1) shows all of the processes, and its idea of free mem does change with pg''s use of its shared segment. So it doesn''t *look* like the ram is hiding in some cgroup. The kernel does not log anything relevant to this. Slabinfo gives some odd output. It seems to think there are negative quantities of some slabs: Name Objects Objsize Space Slabs/Part/Cpu O/S O %Fr %Ef Flg :at-0000016 5632 16 90.1K 18446744073709551363/0/275 256 0 0 100 *a :t-0000048 3386...

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 | awk 'BEGIN {t=0;} {print $1 " " ($3 * $4); t=t+($3 * $4)} END {print "total " t/(1024 * 1024) " MB";}' | column -t

...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 /proc/slabinfo.? You can simplify its > content to bytes per object type and a total: > > ? grep -v ^# /proc/slabinfo | awk 'BEGIN {t=0;} {print $1 " " ($3 * > $4); t=t+($3 * $4)} END {print "total " t/(1024 * 1024) " MB";}' | > column -t The total number from...

...er_head, trying again. >> >> anyone seen this? > > Not an rsync problem. This is a kernel issue. > > You seem to be out of ZONE_DMA memory. I don't know whether > you should be reporting this to RH or Veritas or IBM but > when you do be sure to send them /proc/slabinfo from the > moment of error. > > One thing you might try is booting with mem=900M Running > with more than 900M < n < 1G memory on 2.4 kernels is > problematic. > > I am experiencing this same problem with rsync 2.5.6 and 2.5.7. The difference for me is I am running...

Hi, I'm using linux 2.6.21.5 and our kernel is freeze. The problem is, if I create a Software bridge using $brctl command. and add two interfaces say, eth0.0 and eth0.1 using $brctl addbr br-lan $brctl addif br-lan eth0.0 $brctl addif br-lan eth0.1 and when i send traffic from a host connected to one port to host connected at other end, soon all the memory is dried up and and kernel

Ok here are all the information the website said I should include first: [root@residents root]# shorewall version 1.4.8 [root@residents root]# ip addr show 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100

...e ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ========================================= All my investigation so far led me to believe that it is because skbuff cache getting full. ========================================================================= PROC-SLABINFO skbuff_fclone_cache 227 308 512 7 1 : tunables 54 27 8 : slabdata 44 44 0 skbuff_head_cache 1574 1650 256 15 1 : tunables 120 60 8 : slabdata 110 110 0 SLAB-TOP Active / Total Objects (% used) : 2140910 / 2200115 (97.3%) Active / To...

...to me that perhaps we''re crashing less often because the block request delivery times have improved dramatically, and the queues are likely growing shorter. The only direct evidence that I and one other list member have seen that could be related to this issue is that accessing /dev/slabinfo on a regular basis in the Dom0 appears to greatly increase the frequency of crashes, which leads me to believe that the issue, at its core, is somehow related to SLAB corruption in Dom0. Another list member has also recently reported that this issue appears to be fixed in the unstable line...

...6008 kB SwapFree: 506008 kB Dirty: 88 kB Writeback: 0 kB Mapped: 22724 kB Slab: 83672 kB CommitLimit: 622232 kB Committed_AS: 43236 kB PageTables: 468 kB VmallocTotal: 696312 kB VmallocUsed: 856 kB VmallocChunk: 695416 kB /dev/slabinfo slabinfo - version: 2.1 # name <active_objs> <num_objs> <objsize> <objperslab> <pagesperslab> : tunables <limit> <batchcount> <sharedfactor> : slabdata <active> rpc_buffers 8 8 2048 2 1 : tunables 24 12...

On Sat, 22 Nov 2003 20:57:44 +0530 (GMT+05:30) anand@eis.iisc.ernet.in (SVR Anand) wrote: > Hi, > > I am one of the system administrators who manage a campus network of 5000 users > that is connected to Internet. We have placed a Linux bridge to isolate the > Internet from the campus. To nullify network flooding effect, we have used > iptables. The kernel is 2.6.0-test9, the

>From: "Shawn Wright" <swright@sls.bc.ca> >Subject: [Shorewall-users] Finally making some progress >I *think* we are finally making some progress in tracking our elusive >performance problems. After employing a second 10Mb link from our ISP, >along with another firewall box and proxy, we were able to determine the >problem *is* our firewall. We don''t