10-01-2010
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
tar: Memory allocation failed for extended data while reading : Not enough space
what can be done for the above problem?
top utility reports memory usage as follows:
Memory: Real: 2688M/15G act/tot Virtual: 1492M/42915M use/tot Free: 11G
this cannot be a disk space problem as we have... (1 Reply)
Discussion started by: gfhgfnhhn
1 Replies
2. Programming
I am trying to compile the pro*C file but gives errors. It says it encountered "std" while it was expecting ; , = ( $ $ORACLE_HOME/bin/proc tradewind/dataaccess/Blob.pcc
Pro*C/C++: Release 10.2.0.3.0 - Production on Fri May 9 11:10:54 2008
Copyright (c) 1982, 2005, Oracle. All rights... (0 Replies)
Discussion started by: shafi2all
0 Replies
3. UNIX for Advanced & Expert Users
In our directory there are too many files, & if I try to execute mv *.gz or rm *.l command it fails, providing error string as - 'arg list too long'. This doesnt happen always, is there any way we know, limit on the rm & mv command so we can take care of this failure in future executions ? (9 Replies)
Discussion started by: videsh77
9 Replies
4. AIX
Hi All,
I have a process running on my AIX 5.3 server box. The process runs fine for 5-6days but then crashes. The log file shows malloc failure and the svmon (Virtual memory size), ps -lef (SZ value) are also gradually increasing. But unfortunately MALLOCDEBUG and any other memory debugging... (3 Replies)
Discussion started by: SBatra
3 Replies
5. SuSE
Hi,
My program was running for a whole night. after 12 hours i got an error message "Cannot allocate memory" during the shmat commmand. So can you please let me know what could be the reason? is there any solution?
thanks in advance.
Regards,
Mano (5 Replies)
Discussion started by: ManoharanMani
5 Replies
6. SuSE
Hi,
In my proj, one process was running for 2 days. after 2 days its throwing an error message "shmget failed cannot allocate memory". the same problem happened every time.i.e. i can reproduce the same issue if my process is running for every 2 days for a same operation.Within this 2 days there... (1 Reply)
Discussion started by: ManoharanMani
1 Replies
7. Linux
Hi,
In my proj, one process was running for 2 days. after 2 days its throwing an error message "shmget failed cannot allocate memory". the same problem happened every time.i.e. i can reproduce the same issue if my process is running for every 2 days for a same operation.Within this 2 days there... (1 Reply)
Discussion started by: ManoharanMani
1 Replies
8. Linux
Hi,
In my proj, one process was running for 2 days. after 2 days its throwing an error message "shmget failed cannot allocate memory". the same problem happened every time.i.e. i can reproduce the same issue if my process is running for every 2 days for a same operation.Within this 2 days there... (1 Reply)
Discussion started by: ManoharanMani
1 Replies
9. Red Hat
Hi ,
Our one of VMguest all lvm got unmounted once the machine is rebooted
when in repair state dmesg its showing an error out of memory killed process 22289 (lvm)
please refer screen shots attached
when i look the lvscan its showing all lvm are inactive
i checked throuh top there... (0 Replies)
Discussion started by: venikathir
0 Replies
LEARN ABOUT REDHAT
slabinfo
SLABINFO(5) Linux manual SLABINFO(5)
NAME
/proc/slabinfo - Kernel slab allocator statistics
SYNOPSIS
cat /proc/slabinfo
DESCRIPTION
Frequently used objects in the Linux kernel (buffer heads, inodes, dentries, etc.) have their own cache. The file /proc/slabinfo gives
statistics. For example:
% cat /proc/slabinfo
slabinfo - version: 1.1
kmem_cache 60 78 100 2 2 1
blkdev_requests 5120 5120 96 128 128 1
mnt_cache 20 40 96 1 1 1
inode_cache 7005 14792 480 1598 1849 1
dentry_cache 5469 5880 128 183 196 1
filp 726 760 96 19 19 1
buffer_head 67131 71240 96 1776 1781 1
vm_area_struct 1204 1652 64 23 28 1
...
size-8192 1 17 8192 1 17 2
size-4096 41 73 4096 41 73 1
...
For each slab cache, the cache name, the number of currently active objects, the total number of available objects, the size of each object
in bytes, the number of pages with at least one active object, the total number of allocated pages, and the number of pages per slab are
given.
Note that because of object alignment and slab cache overhead, objects are not normally packed tightly into pages. Pages with even one in-
use object are considered in-use and cannot be freed.
Kernels compiled with slab cache statistics will also have "(statistics)" in the first line of output, and will have 5 additional columns,
namely: the high water mark of active objects; the number of times objects have been allocated; the number of times the cache has grown
(new pages added to this cache); the number of times the cache has been reaped (unused pages removed from this cache); and the number of
times there was an error allocating new pages to this cache. If slab cache statistics are not enabled for this kernel, these columns will
not be shown.
SMP systems will also have "(SMP)" in the first line of output, and will have two additional columns for each slab, reporting the slab
allocation policy for the CPU-local cache (to reduce the need for inter-CPU synchronization when allocating objects from the cache). The
first column is the per-CPU limit: the maximum number of objects that will be cached for each CPU. The second column is the batchcount:
the maximum number of free objects in the global cache that will be transferred to the per-CPU cache if it is empty, or the number of
objects to be returned to the global cache if the per-CPU cache is full.
If both slab cache statistics and SMP are defined, there will be four additional columns, reporting the per-CPU cache statistics. The
first two are the per-CPU cache allocation hit and miss counts: the number of times an object was or was not available in the per-CPU cache
for allocation. The next two are the per-CPU cache free hit and miss counts: the number of times a freed object could or could not fit
within the per-CPU cache limit, before flushing objects to the global cache.
It is possible to tune the SMP per-CPU slab cache limit and batchcount via:
echo "cache_name limit batchcount" > /proc/slabinfo
AVAILABILITY
/proc/slabinfo exists since Linux 2.1.23. SMP per-CPU caches exist since Linux 2.4.0-test3.
FILES
<linux/slab.h>
2001-06-19 SLABINFO(5)